[JBoss JIRA] (ISPN-10379) JCache tck-runner test failures are ignored in Jenkins
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10379?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10379:
-----------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR3)
> JCache tck-runner test failures are ignored in Jenkins
> ------------------------------------------------------
>
> Key: ISPN-10379
> URL: https://issues.jboss.org/browse/ISPN-10379
> Project: Infinispan
> Issue Type: Bug
> Components: Build, Test Suite - Core
> Affects Versions: 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Final
>
>
> This build has 0 failures in Jenkins, but the console log says otherwise:
> https://ci.infinispan.org/job/Infinispan/job/PR-7110/1/
> {noformat}
> [2019-07-02T18:45:17.550Z] 18:45:16.738 [INFO] --- maven-failsafe-plugin:3.0.0-M3:integration-test (tck-embedded) @ infinispan-jcache-tck-runner ---
> [2019-07-02T18:45:17.550Z] 18:45:16.750 [INFO] Failsafe report directory: /home/infinispan/workspace/Infinispan_PR-7110/jcache/tck-runner/target/failsafe-reports-embedded
> ...
> [2019-07-02T18:45:53.348Z] 18:45:53.137 [ERROR] CacheExpiryTest.invokeAllReadThroughEnabledGetOnNonExistentEntry:1202
> [2019-07-02T18:45:53.348Z] Expected: is <0>
> [2019-07-02T18:45:53.348Z] but: was <5>
> [2019-07-02T18:45:53.348Z] 18:45:53.137 [ERROR] CacheExpiryTest.invokeGetValueWithReadThroughForNonExistentEntryShouldCallGetExpiryForCreatedEntry:1110
> [2019-07-02T18:45:53.348Z] Expected: is <0>
> [2019-07-02T18:45:53.348Z] but: was <1>
> [2019-07-02T18:45:53.348Z] 18:45:53.138 [ERROR] CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess:688 expected:<2> but was:<3>
> [2019-07-02T18:45:53.348Z] 18:45:53.138 [INFO]
> [2019-07-02T18:45:53.348Z] 18:45:53.138 [ERROR] Tests run: 491, Failures: 3, Errors: 0, Skipped: 0
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10386) OSGi integration tests never run
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10386?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10386:
-----------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR3)
> OSGi integration tests never run
> --------------------------------
>
> Key: ISPN-10386
> URL: https://issues.jboss.org/browse/ISPN-10386
> Project: Infinispan
> Issue Type: Bug
> Components: Build, Test Suite - Core
> Affects Versions: 10.0.0.Beta3, 9.4.15.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> When we started supporting JDK9, Karaf and Pax-Exam didn't support it yet, so we disabled the OSGi integration tests when running on JDK11.
> When we started building on JDK11 and only running the tests on JDK8 with the {{java8-test}} profile, we didn't update the {{integrationtests-osgi}} POM, so the tests stay disabled regardless of profile.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10481) Add additional type support for Protostream user Marshaller
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10481?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10481:
-----------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR3)
> Add additional type support for Protostream user Marshaller
> -----------------------------------------------------------
>
> Key: ISPN-10481
> URL: https://issues.jboss.org/browse/ISPN-10481
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> The PersistenceMarshallerImpl uses protostream to do marshalling and if not falls back to a user marshaller. The protostream context supports many more JDK built in types that we aren't currently testing for. This would allow a user to not have to supply these themselves.
> An example of known types can be found in the BaseProtoStreamMarshaller class.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10488) Infinispan Version is not printed in Quarkus native mode
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10488?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10488:
-----------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR3)
> Infinispan Version is not printed in Quarkus native mode
> --------------------------------------------------------
>
> Key: ISPN-10488
> URL: https://issues.jboss.org/browse/ISPN-10488
> Project: Infinispan
> Issue Type: Sub-task
> Components: Quarkus
> Affects Versions: 10.0.0.Beta5
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> The client prints out the version of Infinispan at startup. Unfortunately for the client the VERSION String is computed at runtime on each invocation. Unfortunately in native mode we don't have the package implementation version available. Instead we should write this version to a static variable that is readable during native runtime. Note this is already handled for the server as it is written to a static variable.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10521) CacheMgmtInterceptorMBeanTest.testStores random failure
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10521?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10521:
-----------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR3)
> CacheMgmtInterceptorMBeanTest.testStores random failure
> -------------------------------------------------------
>
> Key: ISPN-10521
> URL: https://issues.jboss.org/browse/ISPN-10521
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 10.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Will Burns
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Final
>
> Attachments: ISPN-9541_modules_20190825-1146_CacheMgmtInterceptorMBeanTest-infinispan-core.log.gz
>
>
> The test calls {{TestingUtil.cleanUpDataContainerForCache(cache)}}, but apparently it's still not enough to guarantee that the number of entries is correct:
> {noformat}
> 12:05:33.109 [ERROR] jmx.CacheMgmtInterceptorMBeanTest(org.infinispan.jmx.CacheMgmtInterceptorMBeanTest) Time elapsed: 0.009 s <<< FAILURE!
> java.lang.AssertionError: expecting 4.0 for NumberOfEntries, but received 3
> at org.infinispan.jmx.CacheMgmtInterceptorMBeanTest.assertAttributeValue(CacheMgmtInterceptorMBeanTest.java:228)
> at org.infinispan.jmx.CacheMgmtInterceptorMBeanTest.assertCurrentNumberOfEntries(CacheMgmtInterceptorMBeanTest.java:267)
> at org.infinispan.jmx.CacheMgmtInterceptorMBeanTest.testStores(CacheMgmtInterceptorMBeanTest.java:148)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10522) EvictionWithPassivationTest.testBasicStore random failures
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10522?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10522:
-----------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR3)
> EvictionWithPassivationTest.testBasicStore random failures
> ----------------------------------------------------------
>
> Key: ISPN-10522
> URL: https://issues.jboss.org/browse/ISPN-10522
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 10.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Will Burns
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Final
>
> Attachments: ISPN-10317_pendinglockmanager_20190827-0945_EvictionWithPassivationTest-infinispan-core.log.gz
>
>
> So far it has failed for me every time I debugged the test from the IDE (with trace logging enabled).
> {noformat}
> 09:55:48,837 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.eviction.impl.EvictionWithPassivationTest.testBasicStore[OBJECT]
> java.lang.AssertionError: expected [null] but found [B6]
> at org.testng.Assert.fail(Assert.java:96) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.failNotEquals(Assert.java:776) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.assertEqualsImpl(Assert.java:132) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.assertEquals(Assert.java:118) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.assertEquals(Assert.java:453) ~[testng-6.14.3.jar:?]
> at org.testng.Assert.assertEquals(Assert.java:463) ~[testng-6.14.3.jar:?]
> at org.infinispan.eviction.impl.EvictionWithPassivationTest.testBasicStore(EvictionWithPassivationTest.java:115) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10591) Remove jboss-marshalling and make Protostream the default user marshaller
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10591?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10591:
-----------------------------------
Fix Version/s: 10.0.0.Final
(was: 10.0.0.CR3)
> Remove jboss-marshalling and make Protostream the default user marshaller
> -------------------------------------------------------------------------
>
> Key: ISPN-10591
> URL: https://issues.jboss.org/browse/ISPN-10591
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core
> Affects Versions: 10.0.0.CR1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Protostream should be used as the default marshaller for user types unless a user explicitly provides a custom marshaller via {{SerializationConfiguration.marshaller}}.
> This requires that all of our testsuite is also updated to provide protostream pojos and that the `infinispan-jboss-marshalling` dependency is removed from all possible sub-modules. Most notably:
> * core
> * query
> * server
> * client
> This will require various integration tests to also be updated to reflect the new behaviour, as the APPLICATION_JBOSS_MARSHALLING media type will not be available to the client/server by default.
> In order for a user to utilise jboss-marshalling on the client side, it's necessary for the `infinispan-jboss-marshalling` jar to be added to the classpath. Furthermore, if APPLICATION_OBJECT storage is desired on the server and jboss-marshalling is utilised on the client, it's also necessary for the dependency to be added to the server. In order to verify that this functionality works as expected, it's necessary for a `integrationtests/jboss-marshalling` sub-module to be created in order to test these scenarios.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months