[infinispan-issues] [JBoss JIRA] (ISPN-3367) ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly

[Mircea Markus (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated ISPN-3367:
--------------------------------

    Labels: 630 testsuite_stability  (was: testsuite_stability)

    
> ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly
> --------------------------------------------------------------------------
>
>                 Key: ISPN-3367
>                 URL: https://issues.jboss.org/browse/ISPN-3367
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 6.0.0.Alpha1, 6.0.2.Final
>         Environment: {w2k8r2 OracleJDK1.7}, { RHEL6_x86_64, OracleJDK1.7 and OpenJDK1.7}, {solaris10_x86_64 and solaris10-sparc_x86_64, OracleJDK1.7}
>            Reporter: Vitalii Chepeliuk
>            Assignee: Dan Berindei
>              Labels: 630, testsuite_stability
>             Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
>         Attachments: ClusterTopologyManagerTest.log.zip
>
>
> Error Message
> Thread already timed out waiting for event merge
> Stacktrace
> java.lang.IllegalStateException: Thread already timed out waiting for event merge
> 	at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:131)
> 	at org.infinispan.test.fwk.CheckPoint.triggerForever(CheckPoint.java:120)
> 	at org.infinispan.statetransfer.ClusterTopologyManagerTest.testClusterRecoveryWithRebalance(ClusterTopologyManagerTest.java:280)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> 	at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
> 	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> 	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> 	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> 	at org.testng.TestRunner.privateRun(TestRunner.java:767)
> 	at org.testng.TestRunner.run(TestRunner.java:617)
> 	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> 	at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> 	at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> 	at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:724)
> Add links to jenkins jobs
> windows, OracleJDK1.7>>>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/edg-60-ispn-testsuite-windows/95/jdk=java17_default,label_exp=w2k8r2%20%26%26%20x86_64/testReport/junit/org.infinispan.statetransfer/
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/edg-60-ispn-testsuite-windows/82/jdk=java17_default,label_exp=w2k8r2%20%26%26%20x86_64/testReport/junit/org.infinispan.statetransfer/
> Linux, OracleJDK1.7>>>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/edg-60-ispn-testsuite-rhel/jdk=java17_default,label_exp=RHEL6_x86_64/165/testReport/junit/org.infinispan.statetransfer/
> Linux, OpenJDK1.7>>>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/edg-60-ispn-testsuite-rhel/jdk=openjdk-1.7.0-local,label_exp=RHEL6_x86_64/164/testReport/org.infinispan.statetransfer/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira