Change By: Don Bogardus (12/Dec/14 5:47 PM)
Description: Similar to bug 22641, Jenkins no longer cleaning up  surefire executions  child processes  when a job is stopped. 

To reproduce : Start any job with a surefire execution, once the tests start running, stop the job through the jenkins interface. The surefire process continues to run. 

Just like bug 22641, this behavior started in 1.553, was resolved in 1.565.2, then started again in 1.587. 

Rating this as critical because processes build up eventually causing issues with running out of memory or hitting the nproc limit. 
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to