maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SUREFIRE-1290) Orphan Fork JVMs should be killed after any previous finished with fatal error
Date Sun, 02 Oct 2016 10:35:20 GMT

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

Tibor Digana closed SUREFIRE-1290.
----------------------------------
    Resolution: Fixed

commit
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=33a32d132922e3ab22502f95bb42aeecfe1531fb

> Orphan Fork JVMs should be killed after any previous finished with fatal error
> ------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1290
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1290
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>             Fix For: 2.19.2
>
>
> If you, for instance, run two forks in parallel and the first one abruptly failed with
fatal error then the second JVM should be killed.
> This prevents from errors on deleting {{surefire<hash>.jar}} files. and {{/target/surefire}}
folder.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message