Investigate PairActorTest failure
Reported by Ben Hood | August 10th, 2011 @ 10:20 AM
The test shouldGenerateExceptionInVersionCorrelationWriterProxyWhenAParticipantFails in the PairActorTest seems to fail intermittently (e.g. build 337) with the following stack trace:
java.lang.Exception: Exception validation never reached in participant stub
at net.lshift.diffa.kernel.actors.PairActorTest$$anonfun$shouldGenerateExceptionInVersionCorrelationWriterProxyWhenAParticipantFails$1.apply(PairActorTest.scala:377)
at net.lshift.diffa.kernel.actors.PairActorTest$$anonfun$shouldGenerateExceptionInVersionCorrelationWriterProxyWhenAParticipantFails$1.apply(PairActorTest.scala:377)
at scala.Option.getOrElse(Option.scala:109)
at net.lshift.diffa.kernel.actors.PairActorTest.shouldGenerateExceptionInVersionCorrelationWriterProxyWhenAParticipantFails(PairActorTest.scala:377)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:102)
at org.apache.maven.surefire.Surefire.run(Surefire.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
Comments and changes to this ticket
-
Ben Hood August 24th, 2011 @ 07:10 AM
(from [0174c01d69ea094075522de3c20d81bccacca76d]) [#336] Allocate each test to it's own pair https://github.com/lshift/diffa/commit/0174c01d69ea094075522de3c20d...
-
Paul Jones August 24th, 2011 @ 07:11 AM
I've added a patch for this to make each test use it's own pair. I'm not sure that this is the actual problem though - it should hopefully help to isolate the tests more though.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood