Author martin.panter
Recipients gregory.p.smith, haizaar, martin.panter, xtreak
Date 2019-06-27.08:37:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561624627.2.0.98322031951.issue37424@roundup.psfhosted.org>
In-reply-to
Content
Same thing going on as in Issue 30154. The shell is probably spawning the “sleep” command as a child process (grandchild of Python), and waiting for it to exit. When Python times out, it will kill the shell process, leaving the grandchild as an orphan. The “sleep” process will still be running and probably holds the “stdout” and/or “stderr” pipes open, and Python will wait indefinitely to be sure it has captured all the output to those pipes.

Also see Issue 26534 proposes APIs to kill a process group rather than the single child process.
History
Date User Action Args
2019-06-27 08:37:07martin.pantersetrecipients: + martin.panter, gregory.p.smith, xtreak, haizaar
2019-06-27 08:37:07martin.pantersetmessageid: <1561624627.2.0.98322031951.issue37424@roundup.psfhosted.org>
2019-06-27 08:37:07martin.panterlinkissue37424 messages
2019-06-27 08:37:07martin.pantercreate