<br><div class="gmail_quote">On Mon, Oct 29, 2012 at 5:06 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@infinispan.org" target="_blank">sanne@infinispan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 29 October 2012 08:59, Anna Manukyan <<a href="mailto:amanukya@redhat.com">amanukya@redhat.com</a>> wrote:<br>
> Hi Sanne,<br>
><br>
> sorry for my interfering in - I was lately working on CDI testsuite - evaluating the coverage, etc. and actually on my local environment as well as on Jenkins, the CDI integration tests are passing properly.<br>
<br>
</div>Hi Anna,<br>
I wouldn't call that interfering, it's exactly the kind of feedback I<br>
was looking for. I just checked master again, and it still failed for<br>
me.<br>
This is the stack I have in all tests, in case it helps:<br>
<br>
java.lang.NullPointerException<br>
at org.jboss.arquillian.testng.Arquillian.arquillianAfterClass(Arquillian.java:82)<br>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)<br>
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)<br>
at java.lang.reflect.Method.invoke(Method.java:597)<br>
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74)<br>
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)<br>
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)<br>
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)<br>
at org.testng.internal.TestMethodWorker.invokeAfterClassMethods(TestMethodWorker.java:222)<br>
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)<br>
at org.testng.TestRunner.runWorkers(TestRunner.java:1147)<br>
at org.testng.TestRunner.privateRun(TestRunner.java:749)<br>
at org.testng.TestRunner.run(TestRunner.java:600)<br>
at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)<br>
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312)<br>
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274)<br>
at org.testng.SuiteRunner.run(SuiteRunner.java:223)<br>
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)<br>
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)<br>
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1039)<br>
at org.testng.TestNG.runSuitesLocally(TestNG.java:964)<br>
at org.testng.TestNG.run(TestNG.java:900)<br>
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:77)<br>
<br></blockquote><div><br>This is <a href="https://issues.jboss.org/browse/ARQ-553">https://issues.jboss.org/browse/ARQ-553</a><br><br>Of course, we do specify parallel=none in the CDI pom.xml, but because of a bug in Maven or Surefire, TestNG sometime runs with the parent configuration (parallel=tests). <br>
<br>If you can reproduce it reliably on your machine maybe you can debug Maven and file a bug with them... I was supposed to fix the CDI suite but I never reproduced it on my machine.<br><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Anyway, whatever the state of CDI that looks like a separate problem;<br>
I can't run the core testsuite reliably with this version of TestNG;<br>
from Vladimir's comment I guess we can't upgrade easily<br>
so I'm opening ISPN-2450.<br>
<br>
Cheers,<br>
Sanne<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
><br>
> I've run the tests several times, but I hadn't got the test hangouts as you have mentioned and all tests are passing on my side without failures.<br>
><br>
> I've tried also the testsuite execution with TestNG version 6.7 and it is fine as well.<br>
><br>
> I just thought, maybe there is something wrong with your testsuite setup or environment (just thoughts)?<br>
><br>
> Best regards,<br>
> Anna.<br>
><br>
> ----- Original Message -----<br>
> From: "Sanne Grinovero" <<a href="mailto:sanne@infinispan.org">sanne@infinispan.org</a>><br>
> To: "infinispan -Dev List" <<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a>><br>
> Sent: Sunday, October 28, 2012 11:12:32 AM<br>
> Subject: [infinispan-dev] Testsuite: hanging TestNG, CDI proken<br>
><br>
> Hello all,<br>
><br>
> besides having regular failures, I also experienced occasional hangs<br>
> while running the testsuite; in some cases I found the following stack<br>
> which suggests a TestNG bug:<br>
><br>
> "pool-3-thread-14" prio=10 tid=0x00007f0d84632000 nid=0x1ce5 runnable<br>
> [0x00007f0d58a36000]<br>
> java.lang.Thread.State: RUNNABLE<br>
> at java.util.HashMap.put(HashMap.java:374)<br>
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:320)<br>
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:34)<br>
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351)<br>
> at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147)<br>
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)<br>
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)<br>
> at java.lang.Thread.run(Thread.java:662)<br>
><br>
> Even when taking multiple dumps that thread is still in the same loop,<br>
> and having a single CPU stuck at 100% I'm guessing the HashMap was<br>
> being used in some unsafe way regarding concurrency; we're using the<br>
> first minor version of TestNG which ever supported parallel testsuite<br>
> invocations so that might not be very solid.<br>
><br>
> Not sure why, but upgrading TestNG from 5.14.10 to 6.7 seems to<br>
> resolve the problem.<br>
><br>
> Now I wish I could send a pull request, but even skipping just the<br>
> core testsuite (which always fails for me even in non-parallel mode)<br>
> many other modules are broken both with and without my patches, so I'm<br>
> dropping my experiments as I won't send any pull requests if the tests<br>
> can't back my changes up.<br>
><br>
> As an example the CDI integration is:<br>
><br>
> Tests run: 247, Failures: 102, Errors: 0, Skipped: 143<br>
><br>
> ...which means 2 tests are fine.<br>
><br>
> Cheers,<br>
> Sanne<br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br>