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

Hudson commented on SUREFIRE-1290:
----------------------------------

SUCCESS: Integrated in Jenkins build maven-surefire-junit5 #8 (See 
[https://builds.apache.org/job/maven-surefire-junit5/8/])
[SUREFIRE-1290] Orphan Fork JVMs should be killed after any previous (tibor17: 
rev 33a32d132922e3ab22502f95bb42aeecfe1531fb)
* (edit) 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
* (edit) 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java
* (edit) 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java


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

Reply via email to