[infinispan-issues] [JBoss JIRA] (ISPN-2450) Testsuite hanging because of parallel execution and TestNG bug

[Manik Surtani (JIRA)]

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

Manik Surtani updated ISPN-2450:
--------------------------------

       Fix Version/s: 5.1.9.Final
    Git Pull Request: https://github.com/infinispan/infinispan/pull/1434  (was: https://github.com/infinispan/infinispan/pull/1434)

    
> Testsuite hanging because of parallel execution and TestNG bug
> --------------------------------------------------------------
>
>                 Key: ISPN-2450
>                 URL: https://issues.jboss.org/browse/ISPN-2450
>             Project: Infinispan
>          Issue Type: Task
>            Reporter: Sanne Grinovero
>            Assignee: Manik Surtani
>             Fix For: 5.2.0.Beta3, 5.1.9.Final
>
>
> I've had the testsuit hang frequently recently and it seems this stack is often found in such cases:
> > "pool-3-thread-14" prio=10 tid=0x00007f0d84632000 nid=0x1ce5 runnable
> > [0x00007f0d58a36000]
> >    java.lang.Thread.State: RUNNABLE
> >         at java.util.HashMap.put(HashMap.java:374)
> >         at org.testng.SuiteRunner.runTest(SuiteRunner.java:320)
> >         at org.testng.SuiteRunner.access$000(SuiteRunner.java:34)
> >         at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351)
> >         at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147)
> >         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >         at java.lang.Thread.run(Thread.java:662)
> If after a while I take another thread dump, the thread is still looping around at the same line.
> I couldn't reproduce the problem with TestNG 6.7, not sure if they solved it or if it's just less likely.

--
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