Run subprocess-starting tests without pytest-xdist#30264
Draft
jkseppan wants to merge 1 commit intomatplotlib:mainfrom
Draft
Run subprocess-starting tests without pytest-xdist#30264jkseppan wants to merge 1 commit intomatplotlib:mainfrom
jkseppan wants to merge 1 commit intomatplotlib:mainfrom
Conversation
Member
|
Similar idea at #29981, but it continued using xdist for everything and just moved all subprocess-using tests to a single worker. |
8b4048c to
b817890
Compare
jkseppan
added a commit
to jkseppan/matplotlib
that referenced
this pull request
Jul 6, 2025
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 other long-running tests are executing. This happens often with Python 3.14 tests for some reason. Put the tests that start a subprocess in a separate loadgroup so that no two of them get executed in parallel. Alternative to matplotlib#30264.
ebaa666 to
28eb7a9
Compare
Member
Author
48eb0bf to
7105892
Compare
Member
Author
|
These 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 other long-running tests are executing. This happens often with Python 3.14 tests for some reason. Add a new pytest marker for the tests that start a subprocess at top level, and run these tests in a separate pass without pytest-xdist parallelization.
7105892 to
9518c9b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.