➜

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 giampaolo.rodola, neologix, python-dev, rosslagerwall, vstinner
Date 2011-06-28.00:25:53
SpamBayes Score 3.784339e-07
Marked as misclassified No
Message-id <1309220753.88.0.301103656267.issue12303@psf.upfronthosting.co.za>
In-reply-to
Content 
> test_sigwaitinfo_interrupted() fails because SIGALRM
> signal handler is called ...

Oh, the problem is that sigwait() behaviour changes after a fork: it is interrupted if an unexpected signal is received, but the signal handler is not called. It behaves correctly (the signal handler is called) without the fork.

The correct fix is maybe to avoid the os.fork() instead of skipping the test on FreeBSD 6.
History
Date User Action Args
2011-06-28 00:25:53vstinnersetrecipients: + vstinner, giampaolo.rodola, neologix, rosslagerwall, python-dev
2011-06-28 00:25:53vstinnersetmessageid: <1309220753.88.0.301103656267.issue12303@psf.upfronthosting.co.za>
2011-06-28 00:25:53vstinnerlinkissue12303 messages
2011-06-28 00:25:53vstinnercreate