[issue30314] Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 buildbot

STINNER Victor added the comment: The timeout of buildbot has been adjusted (my PR https://github.com/python/buildmaster-config/pull/8 has been merged). The cpu resource has been disabled on Travis CI to make it faster. This issue can now been fixed. -- resolution: -> fixed stage:

[issue30314] Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 buildbot

Changes by Zachary Ware : -- nosy: +zach.ware ___ Python tracker ___ ___

[issue30314] Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 buildbot

STINNER Victor added the comment: I merged my PR and applied the new buildbot configuration. I will try to check if the config was applied correctly. Serhiy: "test_tools is so slow because it proceeds *all* Python files. This controlled by the "cpu" resource (only 10 random files are chosen

[issue30314] Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 buildbot

Serhiy Storchaka added the comment: test_tools is so slow because it proceeds *all* Python files. This controlled by the "cpu" resource (only 10 random files are chosen if it is disabled). Maybe disable the "cpu" resource on slow buildbots? -- nosy: +serhiy.storchaka

[issue30314] Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 buildbot

STINNER Victor added the comment: PR: https://github.com/python/buildmaster-config/pull/8 -- ___ Python tracker ___

[issue30314] Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 buildbot

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