[
https://jira.codehaus.org/browse/SUREFIRE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307409#comment-307409
]
Ryan Hennig commented on SUREFIRE-870:
--------------------------------------
This is fixed in 2.12.1 and later
> "Error occurred in starting fork" shouldn't be reported for all forks with
> non-zero exit codes
> ----------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-870
> URL: https://jira.codehaus.org/browse/SUREFIRE-870
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.12
> Reporter: Andrew Bayer
> Assignee: Kristian Rosenvold
>
> If a forked test has a non-zero exit code for any reason, it's reported by
> Surefire as "Error occurred in starting fork". It's distinctly possible for a
> forked test to have a non-zero exit code for reasons other than problems
> starting the fork - i.e., a bad test that as a System.exit(1) in it, etc. The
> error should either be more general, or more specific tracing of the problem
> should be done.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
