[
http://jira.codehaus.org/browse/SUREFIRE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258150#action_258150
]
Chad Wilson commented on SUREFIRE-704:
--------------------------------------
It's possible that this is spurious (and it certainly seems bizarre) but we
started getting failures with one of our tests after we added a relatively
simple @Setup to the test. Even more strangely, re-ordering the @Tests in the
file so that the two tests (of 4) that were logging an exception stacktrace via
log4j weren't last in the file seemed to fix it as well. The mind boggles.
We have the same Maven setup as S Daigle.
> maven surefire Error while executing forked tests.; nested exception is
> java.lang.IllegalStateException: testSetStarting called twice
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-704
> URL: http://jira.codehaus.org/browse/SUREFIRE-704
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.7.2
> Environment: Windows/Linux/SunOS
> Reporter: S Daigle
> Attachments: surefire-272.txt, surefire.txt
>
>
> We want to upgrade from our current 2.5 version of the maven-surefire-plugin
> to something newer but cannot get past the error below. We've tried versions
> 2.6, 2.7 up to and including 2.7.3-SNAPSHOT but they all fail.
> When setting forkmode to "once" and redirectTestOutputToFile to "true", we
> get the following error on multiple tests:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.7.3-SNAPSHOT:test
> (default-test) on project api: Error while executing forked tests.; nested
> exception is java.lang.IllegalStateException: testSetStarting called twice ->
> [Help 1]
> Please see the attachment for full "mvn -e test" output.
> If we set the redirectTestOutputToFile to false, it works but we need this
> option set to true.
> Thanks
--
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
