[Python-Dev] Green buildbot failure.

Victor Stinner victor.stinner at gmail.com
Sun Aug 11 23:49:38 CEST 2013

2013/8/11 David Bolen <db3l.net at gmail.com>:
>> Was the test terminated because it took too long?
> Yes, it looks like it.
> This test (and one on the XP-4 buildbot in the same time frame) was
> terminated by an external watchdog script that kills python_d
> processes that have been running for more than 2 hours.  I put the
> script in place (quite a while back) as a workaround for failures that
> would strand a python process, blocking future tests due to files
> remaining in use.  It's a last ditch, crude, sledge-hammer.

test.regrtest uses faulthandler.dump_traceback_later() to stop the
test after a timeout if --timeout command line option is used.


Do you pass this option?

The timeout is not global but one a single function of a test file, so
you can use shorter timeout. It has also the advantage of dumping the
traceback of all Python threads before exiting. It didn't try this
feature recently on Windows, but it is supposed to work :-)


More information about the Python-Dev mailing list