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
Reduce the time test_subprocess takes to complete. #82637
Comments
test_subprocess is one of our long running tests, this slows down CI and buildbots. There is room for improvement in its total execution time. Use this issue as a rollup issue for any such work. we need to keep it reliable, just focus on reducing either user/sys cpu time or wall time. |
Nice. Any idea of the speedup on Travis CI and/or on a specific buildbot worker? |
I assume the CI systems are shared and potentially noisy. It should be easier to look at some logs from slower buildbots. but sadly test_subprocess has fallen off the list of "10 slowest tests" that timing info is supplied for. concurrent.futures, multiprocessing, asyncio, tokenize, etc. all take longer. I still don't expect it to be more than a few seconds. |
the slowest tests on Linux today (with number of seconds prepended on my system that runs the suite serially in 34 seconds on a debug build): 3.01 test_check_output_stdout_arg (test.test_subprocess.ProcessTestCaseNoPoll) ... ok |
fyi - handy command to get that python -m test.regrtest -v test_subprocess | ts '.%s' then process that using whatever you want to compute deltas and sort. i fed the output of that into:
|
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: