[ http://jira.codehaus.org/browse/SUREFIRE-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258491#action_258491 ]
Kristian Rosenvold commented on SUREFIRE-690: --------------------------------------------- OK, this indicates that there are probably several distinct issues causing this problem. You can either add plexus to your surefire-declaration (2.7.2) or just switch to 2.8-SNAPSHOT. Could you give me some indication of the frequency of this issue in its current state ? The redirectTestOuputToFile logice is due for a revision in 2.8.1 or so, and it's basically the source of all these troubles. Is the remaining frequency is more in the "annoyance" category? > 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.8 > > > 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