[JBoss JIRA] (ISPN-8750) CloudCacheStore: bucket name should fulfill s3 requirements
by Vojtech Juranek (JIRA)
Vojtech Juranek created ISPN-8750:
-------------------------------------
Summary: CloudCacheStore: bucket name should fulfill s3 requirements
Key: ISPN-8750
URL: https://issues.jboss.org/browse/ISPN-8750
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Reporter: Vojtech Juranek
Assignee: Vojtech Juranek
{{s3}} bucket name requirements probably has changes and all bucket name characters have to be lower case. Normalize cache names options should ensure that all chars are lower case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (ISPN-8567) Some stress tests run during the regular build
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8567?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8567:
------------------------------------
Fix Version/s: 9.2.0.Final
(was: 9.2.0.CR2)
> Some stress tests run during the regular build
> ----------------------------------------------
>
> Key: ISPN-8567
> URL: https://issues.jboss.org/browse/ISPN-8567
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.2.0.Beta1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.2.0.Final
>
>
> Some stress tests extend non-stress tests and just change some parameters, e.g. {{ConditionalOperationsConcurrentStressTest}}. TestNG uses the groups of the declaring class to decide whether to run a particular method, so methods that are not overridden keep the {{functional}} group and yet run with the "stress" parameters.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (ISPN-8554) Automatically interrupt hung tests
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8554?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8554:
------------------------------------
Fix Version/s: 9.2.0.Final
(was: 9.2.0.CR2)
> Automatically interrupt hung tests
> ----------------------------------
>
> Key: ISPN-8554
> URL: https://issues.jboss.org/browse/ISPN-8554
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Affects Versions: 9.2.0.Beta1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.2.0.Final
>
>
> Tests should always use timed wait, e.g. {{future.get(10, SECONDS)}} instead of {{future.get()}}. However, it's really easy to use the wrong method, and if a deadlock happens the test suite will never finish.
> Jenkins builds do have a timeout, but the timeout kill procedure is not at all investigation-friendly: only the console output survives, the logs and test results don't.
> We can add a listener ({{IHookable}} in TestNG, because regular listeners are not always invoked on the same thread as the test method) to detect when a test has been running for too long and interrupt the test thread. We can even save a thread dump to make the investigation easier.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (ISPN-8518) FunctionalDistributionTest.testDistributionFromNonOwner random failures
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8518?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8518:
------------------------------------
Fix Version/s: 9.2.0.Final
(was: 9.2.0.CR2)
> FunctionalDistributionTest.testDistributionFromNonOwner random failures
> -----------------------------------------------------------------------
>
> Key: ISPN-8518
> URL: https://issues.jboss.org/browse/ISPN-8518
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.2.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Radim Vansa
> Labels: testsuite_stability
> Fix For: 9.2.0.Final
>
>
> Waiting 100ms is not always enough for the write to be applied on all the owners:
> {noformat}
> java.lang.NullPointerException
> at org.infinispan.functional.FunctionalDistributionTest.lambda$iterate$8(FunctionalDistributionTest.java:97)
> at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1380)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at org.infinispan.functional.FunctionalDistributionTest.iterate(FunctionalDistributionTest.java:98)
> at org.infinispan.functional.FunctionalDistributionTest.doTestDistribution(FunctionalDistributionTest.java:77)
> at org.infinispan.functional.FunctionalDistributionTest.testDistributionFromNonOwner(FunctionalDistributionTest.java:66)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (ISPN-8513) DistSyncOnePhaseTxStateTransferTest random failures
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8513?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8513:
------------------------------------
Fix Version/s: 9.2.0.Final
(was: 9.2.0.CR2)
> DistSyncOnePhaseTxStateTransferTest random failures
> ---------------------------------------------------
>
> Key: ISPN-8513
> URL: https://issues.jboss.org/browse/ISPN-8513
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.2.0.Alpha2
> Reporter: Pedro Ruivo
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 9.2.0.Final
>
> Attachments: DistSyncOnePhaseTxStateTransferTest_pr_wburns_offheap_singlenode2_20171030.log.gz
>
>
> {{DistSyncOnePhaseTxStateTransferTest}} sometimes asserts that the x-site transfer has finished in the remote site too early:
> {noformat}
> 17:34:38,464 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.xsite.statetransfer.DistSyncOnePhaseTxStateTransferTest.testCancelStateTransfer[null, tx=false]
> java.lang.AssertionError:
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.8.8.jar:?]
> at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.8.8.jar:?]
> at org.testng.AssertJUnit.assertFalse(AssertJUnit.java:41) ~[testng-6.8.8.jar:?]
> at org.testng.AssertJUnit.assertFalse(AssertJUnit.java:49) ~[testng-6.8.8.jar:?]
> at org.infinispan.xsite.statetransfer.BaseStateTransferTest$20.assertInCache(BaseStateTransferTest.java:601) ~[test-classes/:?]
> at org.infinispan.xsite.AbstractXSiteTest.assertInSite(AbstractXSiteTest.java:172) ~[test-classes/:?]
> at org.infinispan.xsite.statetransfer.BaseStateTransferTest.assertNoStateTransferInReceivingSite(BaseStateTransferTest.java:596) ~[test-classes/:?]
> at org.infinispan.xsite.statetransfer.BaseStateTransferTest.testCancelStateTransfer(BaseStateTransferTest.java:141) ~[test-classes/:?]
> {noformat}
> In fact, this part of the test seems to let the state transfer finish normally instead of cancelling it, so it could use some logs/comments to explain what's going on.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (ISPN-8487) Global MBean registration happens too soon
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-8487?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-8487:
------------------------------------
Fix Version/s: 9.2.0.Final
(was: 9.2.0.CR2)
> Global MBean registration happens too soon
> ------------------------------------------
>
> Key: ISPN-8487
> URL: https://issues.jboss.org/browse/ISPN-8487
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.2.0.Alpha2
> Reporter: Dan Berindei
> Fix For: 9.2.0.Final
>
>
> Currently {{DefaultCacheManager}} explicitly starts {{CacheManagerJmxRegistration}} before calling {{ModuleLifecycle#cacheManagerStarting}}, which means MBeans in other modules are not registered in JMX.
> We should start {{CacheManagerJmxRegistration}} only during global component registry start, after the modules have registered their components. If we want to make the cache manager available in JMX before {{DefaultCacheManager.start()}}, we should only register that particular MBean. Conversely, on shutdown, components other than the cache manager should be removed from JMX on {{DefaultCacheManager.stop()}} (as per ISPN-118).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months