[jira] [Updated] (SUREFIRE-2095) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true when run with failsafe

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SUREFIRE-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated SUREFIRE-2095:
-------------------------------------
    Fix Version/s: 3.0.0-M9
                       (was: 3.0.0-M8)

> Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true when run with failsafe
> ------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-2095
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-2095
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, process forking
>            Reporter: Aaron Braunstein
>            Assignee: Olivier Lamy
>            Priority: Major
>             Fix For: 3.0.0-M9
>
>
> When tests are run with failsafe that crash the JVM, if the maven.test.failure.ignore option is enabled the verify goal does not fail. Additionally, the error and failure counts in the report summary XML are 0. Together this means that the build succeeds despite some test(s) failing and some tests potentially not even being run whatsoever - and a CI like Jenkins won't mark the build as unstable either.
> SUREFIRE-1426 fixed this for tests run with the surefire plugin, but due to differences with how test reporting works in the failsafe plugin (tests are first run in the integration-test goal then actually checked for failures in the verify goal), the issue is still present.
> Affected tests show within the failsafe summary XML failureMessage: {{SurefireBooterForkException}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)