RetroSearch Browse

Sat Jan 23 02:47:14 EST 2016 · https://mail.python.org/pipermail/python-dev/2016-January/142887.html

On Sat, Jan 23, 2016 at 5:39 PM, Zachary Ware
<zachary.ware+pydev at gmail.com> wrote:
> On Sat, Jan 23, 2016 at 12:03 AM, Chris Angelico <rosuav at gmail.com> wrote:
>> By the way, this looks odd:
>>
>> make buildbottest TESTOPTS= TESTPYTHONOPTS= TESTTIMEOUT=3600
>>  in dir /root/buildarea/3.x.angelico-debian-amd64/build (timeout 3900 secs)
>>
>> The parameter says 3600 (which corresponds to the error message at the
>> end), but it echoes back that the timeout is 3900 seconds.
>
> I'm no help on the main issue, but to explain the timeout difference:
> TESTTIMEOUT is a makefile variable that sets the faulthandler timeout
> that tries to make Python bail out with a stack trace instead of
> letting buildbot kill Python silently.  The 3900 second timeout is
> buildbot's "there's been no output in this long, assume it's hung and
> kill it" timeout.  The difference between the two is to give
> faulthandler a chance to do its thing.

Ah, cool. That's one mystery cleared up, at least.

ChrisA

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-January/142887.html below:

[Python-Dev] Buildbot timing out - test suite failure