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 skrah
Recipients aimacintyre, eric.smith, gpolo, mark.dickinson, r.david.murray, skrah, vstinner
Date 2010-04-23.16:15:14
SpamBayes Score 3.896028e-05
Marked as misclassified No
Message-id <1272039316.78.0.287133138644.issue8424@psf.upfronthosting.co.za>
In-reply-to
Content
The buildbots are generally happy with the change. However, on OpenBSD
test_itimer_prof fails seemingly unrelated to machine load.

I'm not so familiar with the signal module, but how can the signal
handlers in the tests be guaranteed to work? For example, if you
set a variable inside a signal handler (self.hndl_called=True), it
should be a sig_atomic_t. If you call a function, it should be listed
as signal-safe ( 
http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html ),
but setitimer is not.


I say this because there might be further assumptions in the tests
that could generate hard to track down failures in the future.
History
Date User Action Args
2010-04-23 16:15:17skrahsetrecipients: + skrah, aimacintyre, mark.dickinson, vstinner, eric.smith, gpolo, r.david.murray
2010-04-23 16:15:16skrahsetmessageid: <1272039316.78.0.287133138644.issue8424@psf.upfronthosting.co.za>
2010-04-23 16:15:14skrahlinkissue8424 messages
2010-04-23 16:15:14skrahcreate