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 vstinner
Recipients vstinner
Date 2017-08-10.10:08:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502359704.34.0.940745964628.issue31173@psf.upfronthosting.co.za>
In-reply-to
Content
https://github.com/python/cpython/pull/3055 removes the functional test and replaces it with an unit test which mocks os.waitpid() using a new _testcapi.W_STOPCODE() function to test the WIFSTOPPED() path.

The functional test created a core dump, but it's now fixed using SuppressCrashReport. It leaks a zombie process in a special state, the process is traced and cannot be killed. I tried to wait for the process a second time, but it's not enough to "close" it. I guess that we would have to write a little debugger to attach the process in the parent process. IMHO it's overcomplicated just to check that subprocess calls WIFSTOPPED().
History
Date User Action Args
2017-08-10 10:08:24vstinnersetrecipients: + vstinner
2017-08-10 10:08:24vstinnersetmessageid: <1502359704.34.0.940745964628.issue31173@psf.upfronthosting.co.za>
2017-08-10 10:08:24vstinnerlinkissue31173 messages
2017-08-10 10:08:24vstinnercreate