[JIRA] (JENKINS-55867) sh step termination is never detected if the wrapper process is killed

[roman.donche...@intel.com (JIRA)]

Title: Message Title

Roman Donchenko created an issue   Jenkins / JENKINS-55867 sh step termination is never detected if the wrapper process is killed Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-01-30 13:23 Environment: Jenkins 2.150.2 Durable Task Plugin 1.28 Priority: Major Reporter: Roman Donchenko When you execute a shell step, Jenkins runs a wrapper shell process that's responsible for saving the exit code of your script. If this process is killed, then Jenkins never discovers that your script has terminated, and the step hangs forever. This can be easily demonstrated by killing the wrapper process yourself: node() {      sh 'kill $PPID' } Run this pipeline and the sh step will never terminate. I believe this happens due to a bug in the log-touching subshell spawned by the wrapper process. Specifically, the subshell checks whether the wrapper process is still alive with this _expression_: \( -d /proc/$pid -o \! -d /proc/$$ \) But $$ expands to the PID of the parent shell, not the subshell. This means that $pid and $$ are the same thing, and the whole _expression_ always evaluates to true. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.