maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Monica Batra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-870) "Error occurred in starting fork" shouldn't be reported for all forks with non-zero exit codes
Date Wed, 02 Dec 2015 00:18:11 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034943#comment-15034943
] 

Monica Batra commented on SUREFIRE-870:
---------------------------------------

Yes we are having the same issue as described in surefire-1197. In our case, it's happening
on Linux server.

> "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)

Mime
View raw message