Message140243
| Author |
vstinner |
| Recipients |
vstinner |
| Date |
2011年07月13日.10:14:10 |
| SpamBayes Score |
1.7264668e-07 |
| Marked as misclassified |
No |
| Message-id |
<1310552052.01.0.62401562822.issue12550@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Sometimes, some tests are stopped because of SIGALRM. A recent example:
-----------------------
[157/357] test_socketserver
Alarm clock
*** Error code 142
-----------------------
http://www.python.org/dev/buildbot/all/builders/x86%20FreeBSD%206.4%203.x/builds/1647/steps/test/logs/stdio
faulthandler is able to dump the Python backtrace in such case, we just have to register the SIGALRM signal handler. regrtest should be patched: just add faulthandler.register(signal.SIGALRM).
It would be nice if faulthandler calls the previous signal handler. By default, it replaces the existing signal handler and so it changes the behaviour.
A test should also be added to faulthandler for SIGALRM, this signal is special because of its default signal handler (it exits the process). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年07月13日 10:14:12 | vstinner | set | recipients:
+ vstinner |
| 2011年07月13日 10:14:12 | vstinner | set | messageid: <1310552052.01.0.62401562822.issue12550@psf.upfronthosting.co.za> |
| 2011年07月13日 10:14:11 | vstinner | link | issue12550 messages |
| 2011年07月13日 10:14:10 | vstinner | create |
|