Author vstinner
Recipients bapt, koobs, martin.panter, python-dev, vstinner
Date 2015-12-15.10:42:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450176156.16.0.696592136116.issue25868@psf.upfronthosting.co.za>
In-reply-to
Content
> With the pipe, there is still a potential race after the parent writes to the pipe and before sigwaitinfo() is invoked, versus the child sleep() call.

Yeah, I know, that's why I kept the ugly 100 ms sleep.

> What do you think of my suggestion to block the signal? Then (in theory) it should be robust, rather than relying on timing.
> https://bugs.python.org/issue25277#msg256278

I read your comment, but with this change, I'm not sure anymore that we test that sigwaitinfo() retries when it's interrupted by a signal (EINTR).
History
Date User Action Args
2015-12-15 10:42:36vstinnersetrecipients: + vstinner, python-dev, martin.panter, koobs, bapt
2015-12-15 10:42:36vstinnersetmessageid: <1450176156.16.0.696592136116.issue25868@psf.upfronthosting.co.za>
2015-12-15 10:42:36vstinnerlinkissue25868 messages
2015-12-15 10:42:35vstinnercreate