New submission from STINNER Victor: We should give more than 15 min to the "x86 Tiger 3.6" buildbot, since test_tools was killed by the timeout. On the previous build, test_tools took min 25 sec.
The global 15 min timeout was designed to detect deadlocks issues, but here it's just that the buildbot is sometimes too slow. Maybe we should increase the timeout to 30 min on all buildbots, but also increase the timeout of the "tests" step to long than 1 hour? Otherwise, the test can be killed by buildbot without logging the Python traceback. Maybe we can configured buildbot to first send a signal (SIGUSR1? SIGINT?) before killing the process to dump a traceback, but that's something different. --- 0:15:54 [ 52/405] test_tools crashed -- running: test_zipfile (178 sec) Timeout (0:15:00)! Thread 0xa000d000 (most recent call first): File "/Users/db3l/buildarea/3.6.bolen-tiger/build/Lib/ast.py", line 101 in <genexpr> ... File "/Users/db3l/buildarea/3.6.bolen-tiger/build/Lib/test/test_tools/test_unparse.py", line 124 in assertASTEqual ... --- http://buildbot.python.org/all/builders/x86%20Tiger%203.6/builds/349/steps/test/logs/stdio See also bpo-30172: "test_tools takes longer than 5 minutes on some buildbots". ---------- messages: 293316 nosy: haypo priority: normal severity: normal status: open title: Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 buildbot _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30314> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
