Test failure on the current master

11 views
Skip to first unread message

Nicolas A. Bérard-Nault

unread,
May 8, 2012, 11:07:48 PM5/8/12
to Axon Framework Users
There is a test failure on the current master (fetched from github
today). Oddly enough, this failure occurs only when I run the tests
from the console, using maven (mvn clean install). The test does not
fail when I run it in Eclipse, which makes me think it might be caused
by some sort of interaction between tests.

I'm not familiar enough with the code, so I'm giving you guys a heads
up. Here is the stack trace:

-------------------------------------------------------------------------------
Test set:
org.axonframework.commandhandling.annotation.CurrentUnitOfWorkParameterResolverFactoryTest
-------------------------------------------------------------------------------
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.006
sec <<< FAILURE!
testMatches(org.axonframework.commandhandling.annotation.CurrentUnitOfWorkParameterResolverFactoryTest)
Time elapsed: 0.001 sec <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertFalse(Assert.java:68)
at org.junit.Assert.assertFalse(Assert.java:79)
at
org.axonframework.commandhandling.annotation.CurrentUnitOfWorkParameterResolverFactoryTest.testMatches(CurrentUnitOfWorkParameterResolverFactoryTest.java:
62)
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:601)
at org.junit.runners.model.FrameworkMethod
$1.runReflectiveCall(FrameworkMethod.java:45)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:
15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:
42)
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.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:
68)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:
47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:
234)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:
133)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:
114)
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:601)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:
188)
at org.apache.maven.surefire.booter.ProviderFactory
$ProviderProxy.invoke(ProviderFactory.java:166)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:
86)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:
101)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:
74)

Allard Buijze

unread,
May 9, 2012, 2:45:10 AM5/9/12
to axonfr...@googlegroups.com
Hi Nicolas,

thanks for the heads-up! I forgot to push some commits to github, so it should work now. Let me know if it doesn't.
You're right, there is some test influencing another. A UnitOfWork is started somewhere, but not properly stopped. I didn't take the time yet to figure out in which of the 600 tests it is.

Cheers,

Allard
Reply all
Reply to author
Forward
0 new messages