This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients gabriele.trombetti, gregory.p.smith, neologix, python-dev, rosslagerwall, vstinner
Date 2011-08-18.22:32:05
SpamBayes Score 1.2293495e-05
Marked as misclassified No
Message-id <1313706726.54.0.502742353387.issue12650@psf.upfronthosting.co.za>
In-reply-to
Content
> This means that the child process didn't get reaped by _cleanup().

The most likely cause is that when _cleanup() calls waitpid(pid, WNOHANG), the child process hasn't exited yet.
Since I had already set a rather high timeout to avoid this problem and we're only interested in checking that the child is correctly added to the _active list, I've removed the part of test_zombie_fast_process_del which checked that the child got collected when the next Popen instance is allocated (I added this check in test_leak_fast_process_del_killed, which doesn't have this timeout problem because the process gets killed).
I'll watch the buildbots.
History
Date User Action Args
2011-08-18 22:32:06neologixsetrecipients: + neologix, gregory.p.smith, vstinner, rosslagerwall, python-dev, gabriele.trombetti
2011-08-18 22:32:06neologixsetmessageid: <1313706726.54.0.502742353387.issue12650@psf.upfronthosting.co.za>
2011-08-18 22:32:05neologixlinkissue12650 messages
2011-08-18 22:32:05neologixcreate