Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default test suit has undeterministic behaviour on win8 + JDK7 #505

Closed
mrlogan opened this issue Sep 18, 2012 · 6 comments
Closed

Default test suit has undeterministic behaviour on win8 + JDK7 #505

mrlogan opened this issue Sep 18, 2012 · 6 comments

Comments

@mrlogan
Copy link

mrlogan commented Sep 18, 2012

It seems I have found similiar issue like: https://github.com/KentBeck/junit/issues/429 only in my case it happens on Win8 (developer preview). It happens in underministic way, it can pass few times, later it can fail few times in row, or it can mix.

c:\bin>java -version
java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b05)
Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)

c:\bin>java org.junit.runner.JUnitCore org.junit.tests.AllTests
JUnit version 4.10
................................................................................
................................................................................
................................................................................
.............................................................I....I.............
................................................................................
...........................................................................I....
E..........................................................
Time: 5,484
There was 1 failure:

  1. useChildHarvester(org.junit.tests.running.classes.ParentRunnerTest)
    org.junit.ComparisonFailure: expected:<before [apple after before banana] after
    afterAll > but was:<before [banana after before apple] after afterAll >
    at org.junit.Assert.assertEquals(Assert.java:125)
    at org.junit.Assert.assertEquals(Assert.java:147)
    at org.junit.tests.running.classes.ParentRunnerTest.useChildHarvester(Pa
    rentRunnerTest.java:58)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(Framework
    Method.java:45)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCal
    lable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMe
    thod.java:42)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMet
    hod.java:20)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRun
    ner.java:68)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRun
    ner.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.junit.runners.Suite.runChild(Suite.java:128)
    at org.junit.runners.Suite.runChild(Suite.java:24)
    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.junit.runners.Suite.runChild(Suite.java:128)
    at org.junit.runners.Suite.runChild(Suite.java:24)
    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.junit.runner.JUnitCore.run(JUnitCore.java:157)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:136)
    at org.junit.runner.JUnitCore.run(JUnitCore.java:117)
    at org.junit.runner.JUnitCore.runMain(JUnitCore.java:98)
    at org.junit.runner.JUnitCore.runMainAndExit(JUnitCore.java:53)
    at org.junit.runner.JUnitCore.main(JUnitCore.java:45)

FAILURES!!!
Tests run: 535, Failures: 1

@dsaff
Copy link
Member

dsaff commented Sep 19, 2012

I believe this will be fixed in 4.11

@lennartdiedrich
Copy link

Does anyone has a clue when 4.11 will be released?

@dsaff
Copy link
Member

dsaff commented Sep 20, 2012

https://github.com/KentBeck/junit/issues/332 is where we're starting to try to build momentum for a release.

@marcphilipp
Copy link
Member

I just created a new issue to track the progress of the 4.11 release: #512.

@kcooney
Copy link
Member

kcooney commented Jan 29, 2014

Was this fixed in 4.11?

@dsaff
Copy link
Member

dsaff commented Jan 29, 2014

Yes.

@dsaff dsaff closed this as completed Jan 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants