[
http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260106#action_260106
]
Gin-Ting Chen commented on SUREFIRE-690:
----------------------------------------
I got this again in 2.8.
I should note, however, that I also turned the timeout back on when I updated
to 2.8.
Do you need a stack trace? I can probably get one pretty quickly with the
frequency of this bug
{noformat}
[18:16:29]: [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.8:test (default-test) on
project chameleon-main: Error while executing forked tests.; nested exception
is java.lang.IllegalStateException: testSetStarting called twice -> [Help 1]
[18:16:29]: [ERROR]
[18:16:29]: [ERROR] To see the full stack trace of the errors, re-run Maven
with the -e switch.
[18:16:29]: [ERROR] Re-run Maven using the -X switch to enable full debug
logging.
[18:16:29]: [ERROR]
[18:16:29]: [ERROR] For more information about the errors and possible
solutions, please read the following articles:
[18:16:29]: [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[18:16:29]: [ERROR]
[18:16:29]: [ERROR] After correcting the problems, you can resume the build
with the command
[18:16:29]: [ERROR] mvn <goals> -rf :chameleon-main
{noformat}
> 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
>
> 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
