New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 buildbot #74499
Comments
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. --- See also bpo-30172: "test_tools takes longer than 5 minutes on some buildbots". |
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? |
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 if it is disabled)." I created the bpo-30417 to track this idea. |
The timeout of buildbot has been adjusted (my PR python/buildmaster-config#8 has been merged). The cpu resource has been disabled on Travis CI to make it faster. This issue can now been fixed. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: