Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Run subprocess-starting tests without pytest-xdist#30264
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
rcomer commentedJul 5, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Similar idea at#29981, but it continued using xdist for everything and just moved all subprocess-using tests to a single worker. |
8b4048c
tob817890
CompareI suspect that we are running out of process IDs, or the scheduleris not letting all subprocesses execute, leading to timeouts intests that start subprocesses when other long-running tests areexecuting. This happens often with Python 3.14 tests for some reason.Put the tests that start a subprocess in a separate loadgroupso that no two of them get executed in parallel.Alternative tomatplotlib#30264.
ebaa666
to28eb7a9
CompareI suspect that we are running out of process IDs, or the scheduleris not letting all subprocesses execute, leading to timeouts intests that start subprocesses when other long-running tests areexecuting. This happens often with Python 3.14 tests for some reason.Add a new pytest marker for the tests that start a subprocess attop level, and run these tests in a separate pass withoutpytest-xdist parallelization.
48eb0bf
to7105892
CompareThese still get stuck. Yet another idea: run the tests in separate runner instances (in case we are running out of CPU time or some resource like that on the single instance)#30278 |
I suspect that we are running out of process IDs, or the scheduler
is not letting all subprocesses execute, leading to timeouts in
tests that start subprocesses when there are other tests executing.
This happens often with Python 3.14 tests for some reason.