New submission from STINNER Victor <victor.stin...@haypocalc.com>: 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). ---------- components: Tests messages: 140243 nosy: haypo priority: normal severity: normal status: open title: regrtest: register SIGALRM signal using faulthandler type: crash versions: Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12550> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
