[Python-Dev] Green buildbot failure.

David Bolen db3l.net at gmail.com
Sun Aug 11 23:10:58 CEST 2013

Richard Oudkerk <shibturn at gmail.com> writes:

> On 11/08/2013 11:00am, Antoine Pitrou wrote:
>> You've got the answer at the bottom:
>>    "program finished with exit code 0"
>> So for some reason, the test suite crashed, but with a successful exit
>> code. Buildbot thinks it ran fine.
> 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.

Historically, if this code ran, the buildbot had already itself timed
out, so the exit code (which I can't control) wasn't very important.
2 hours had been conservative (and a trade-off as longer values also
risks failing more future tests) but it may need to be increased.

In this particular case it was a false alarm - the host was heavily
loaded during this time frame, which I think prolonged the test time
by an unusually large amount.

-- David

More information about the Python-Dev mailing list