[
http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255497#action_255497
]
Kristian Rosenvold commented on SUREFIRE-690:
---------------------------------------------
This is basically caused by buffered standard output from the forked test that
is buffered by the os long enough to arrive after the process has terminated. A
very simple workaround while waiting for a fix would be to put something like
Thread.sleep(30) in an @After method.
> testSetCompleted called before testSetStarting when using m3 parallel builds
> ----------------------------------------------------------------------------
>
> Key: SUREFIRE-690
> URL: http://jira.codehaus.org/browse/SUREFIRE-690
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support
> Affects Versions: 2.7.1
> Reporter: Gin-Ting Chen
> Assignee: Kristian Rosenvold
> Fix For: 2.7.3
>
>
> This is running m3 with -T 1C (8 core build machine).
> [17:52:38]: [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on
> project hornet-stinger: Error while executing forked tests.; nested exception
> is java.lang.IllegalStateException: testSetCompleted called before
> testSetStarting -> [Help 1]
> Seems like it doesn't happen as frequently as previously
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
