[JIRA] [durable-task-plugin] (JENKINS-34119) Shell process killed (OOM), but pipeline continues anyway
Title: Message Title Jesse Glick commented on JENKINS-34119 Re: Shell process killed (OOM), but pipeline continues anyway Sounds more like a Linux bug than a problem with Jenkins. If the process is killed by the kernel but the kernel indicates an exit status of zero, what else are we supposed to do? Even if this plugin’s wrapper script were changed to a native program that asked about WIFSIGNALED etc. (reference), your very example would still not work, because neither the wrapped shell script nor bin/mvn are going to care about such subtleties. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [durable-task-plugin] (JENKINS-34119) Shell process killed (OOM), but pipeline continues anyway
Title: Message Title magnayn created an issue Jenkins / JENKINS-34119 Shell process killed (OOM), but pipeline continues anyway Issue Type: Bug Assignee: Jesse Glick Components: durable-task-plugin Created: 2016/Apr/08 10:01 AM Environment: linux Priority: Major Reporter: magnayn I have a jenkins pipeline, that invokes mvn with a 'sh mvn ' invocation. Occasionally, the output shows the maven execution suddenly stop, and the pipeline continuing anyway (failing later because the maven part hadn't actually completed). I haven't been able to confirm, but my strong suspicion is mvn has been killed by the linux OOM killer. Digging in SO, when processes are killed in this way, the 'return code' alone isn't valid. (http://stackoverflow.com/questions/7180970/return-code-when-oom-killer-kills-a-process). I'm not sure the best way to figure this out, as of course bash is calling a script (mvn) which is in turn calling java (the actual maven process that'd be the one being killed).
