[
https://issues.apache.org/jira/browse/SUREFIRE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032653#comment-15032653
]
Monica Batra commented on SUREFIRE-870:
---------------------------------------
Same error is being reported with surefire version 2.19.
> "Error occurred in starting fork" shouldn't be reported for all forks with
> non-zero exit codes
> ----------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-870
> URL: https://issues.apache.org/jira/browse/SUREFIRE-870
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.12
> Reporter: Andrew Bayer
> Assignee: Kristian Rosenvold
> Fix For: 2.12.1
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
