Run subprocess-starting tests on separate runners#30278
Closed
jkseppan wants to merge 6 commits into
Closed
Conversation
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 separate runners without pytest-xdist parallelization.
- set PYTHONUNBUFFERED=1 to make the subprocess Python unbuffered - set bufsize=0 making the parent process pipe unbuffered - because that can return short reads, check if the subprocess exited, and if not, yield the CPU - set stdin to DEVNULL and stderr to STDOUT to avoid blocking related to those
Member
|
Our timeouts are mostly fixed now. |
Member
|
Our timeouts are mostly fixed now. |
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
2 participants
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 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 separate runners without
pytest-xdist parallelization.