[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-7011:
------------------------------------
A simpler alternative to the `@InTransactionMode` annotation might be to check the tx mode in the test, similar to using {{Assume}} in JUnit:
http://blog.xebia.com/conditionally-running-tests-in-testng/
> @AfterClass cleanup doesn't work with @InTransactionMode
> --------------------------------------------------------
>
> Key: ISPN-7011
> URL: https://issues.jboss.org/browse/ISPN-7011
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Labels: testsuite_stability
> Fix For: 9.0.0.Beta1
>
>
> Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation).
> Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure:
> {noformat}
> java.lang.IllegalStateException: Two tests with the same name running in parallel: test
> at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88)
> at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
> at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ]
Dan Berindei edited comment on ISPN-7011 at 9/12/16 2:17 PM:
-------------------------------------------------------------
TestNG 6.9.10.Final seems to run the `@AfterClass` methods properly, but upgrading changes the test method names in IntelliJ to {{api.mvcc.PutForExternalReadTest \(x\)}}.
was (Author: dan.berindei):
TestNG 6.9.10.Final seems to run the `@AfterClass` methods properly, but upgrading changes the test method names in IntelliJ to {{api.mvcc.PutForExternalReadTest (x)}}.
> @AfterClass cleanup doesn't work with @InTransactionMode
> --------------------------------------------------------
>
> Key: ISPN-7011
> URL: https://issues.jboss.org/browse/ISPN-7011
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Labels: testsuite_stability
> Fix For: 9.0.0.Beta1
>
>
> Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation).
> Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure:
> {noformat}
> java.lang.IllegalStateException: Two tests with the same name running in parallel: test
> at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88)
> at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
> at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-7011:
------------------------------------
TestNG 6.9.10.Final seems to run the `@AfterClass` methods properly, but upgrading changes the test method names in IntelliJ to {{api.mvcc.PutForExternalReadTest (x)}}.
> @AfterClass cleanup doesn't work with @InTransactionMode
> --------------------------------------------------------
>
> Key: ISPN-7011
> URL: https://issues.jboss.org/browse/ISPN-7011
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Labels: testsuite_stability
> Fix For: 9.0.0.Beta1
>
>
> Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation).
> Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure:
> {noformat}
> java.lang.IllegalStateException: Two tests with the same name running in parallel: test
> at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88)
> at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
> at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-7011?page=com.atlassian.jira.plugin.... ]
Dan Berindei reassigned ISPN-7011:
----------------------------------
Assignee: Dan Berindei
> @AfterClass cleanup doesn't work with @InTransactionMode
> --------------------------------------------------------
>
> Key: ISPN-7011
> URL: https://issues.jboss.org/browse/ISPN-7011
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Labels: testsuite_stability
> Fix For: 9.0.0.Beta1
>
>
> Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation).
> Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure:
> {noformat}
> java.lang.IllegalStateException: Two tests with the same name running in parallel: test
> at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88)
> at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
> at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (ISPN-7011) @AfterClass cleanup doesn't work with @InTransactionMode
by Dan Berindei (JIRA)
Dan Berindei created ISPN-7011:
----------------------------------
Summary: @AfterClass cleanup doesn't work with @InTransactionMode
Key: ISPN-7011
URL: https://issues.jboss.org/browse/ISPN-7011
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Core
Reporter: Dan Berindei
Priority: Minor
Fix For: 9.0.0.Beta1
Very much like ISPN-7003, TestNG's {{TestMethodWorker.invokeAfterClassMethods}} never sees an empty list of methods in {{m_classMethodMap}}. That happens because {{m_classMethodMap}} is populated before our {{ChainMethodInterceptor}} had a chance to filter the methods (e.g. when a test method has an {{@InTransactionMode}} annotation).
Normally this is not a problem because each test has a different name, and the test suite tolerates some leaked managers. But when you run a test like {{PutForExternalReadTest}} with {{-Dtest.infinispan.shortTestName=true}}, you get this failure:
{noformat}
java.lang.IllegalStateException: Two tests with the same name running in parallel: test
at org.infinispan.test.fwk.TestResourceTracker.testStarted(TestResourceTracker.java:88)
at org.infinispan.test.AbstractInfinispanTest.testClassStarted(AbstractInfinispanTest.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:138)
at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:175)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:107)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (ISPN-5123) MultiNodeDistributedTest deadlock
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-5123?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-5123:
------------------------------------
Attachment: deadlock_sep_10.txt
> MultiNodeDistributedTest deadlock
> ---------------------------------
>
> Key: ISPN-5123
> URL: https://issues.jboss.org/browse/ISPN-5123
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Query
> Affects Versions: 7.1.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Attachments: deadlock_sep_10.txt, infinispan-infinispan-query.log, trace.tar.gz
>
>
> I've been seeing this intermittent problem in my environment. Sometimes the query suite hangs for 30min (and then proceeds). See attached stack trace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months
[JBoss JIRA] (ISPN-5123) MultiNodeDistributedTest deadlock
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-5123?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-5123:
-----------------------------------------
Last stack trace with the deadlock shows several threads waiting for the view and another trying to stop the component registry:
{noformat}
"testng-MultiNodeReplicatedTest" #11 prio=5 os_prio=0 tid=0x00007fcf0c87e000 nid=0x3276 waiting on condition [0x00007fcee18e7000]
- locked <0x0000000087b59758> (a org.infinispan.factories.ComponentRegistry)
"OOB-3,MultiNodeReplicatedTest-NodeC-40758" #45486 prio=5 os_prio=0 tid=0x00007fcecc5ac800 nid=0x6636 waiting on condition [0x00007fce98205000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x0000000087b41f18> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.waitForView(JGroupsTransport.java:260)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.waitForView(JGroupsTransport.java:248)
at org.infinispan.topology.LocalTopologyManagerImpl.waitForView(LocalTopologyManagerImpl.java:545)
"OOB-6,MultiNodeReplicatedTest-NodeC-40758" #89735 prio=5 os_prio=0 tid=0x00007fcecc45c800 nid=0x16c7 waiting on condition [0x00007fcead85a000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x0000000087b41f18> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.waitForView(JGroupsTransport.java:260)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.waitForView(JGroupsTransport.java:248)
at org.infinispan.topology.LocalTopologyManagerImpl.waitForView(LocalTopologyManagerImpl.java:545)
{noformat}
> MultiNodeDistributedTest deadlock
> ---------------------------------
>
> Key: ISPN-5123
> URL: https://issues.jboss.org/browse/ISPN-5123
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Query
> Affects Versions: 7.1.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Attachments: infinispan-infinispan-query.log, trace.tar.gz
>
>
> I've been seeing this intermittent problem in my environment. Sometimes the query suite hangs for 30min (and then proceeds). See attached stack trace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 12 months