Repository navigation
Run the tests with forkserver on Linux - #4818
Merged
alejoe91 merged 1 commit intoOct 5, 2026
Merged
Conversation
h-mayorquin
added
core
alejoe91
approved these changes
Oct 5, 2026
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.
In #4422 we agreed that at minimum we should run the tests with
forkserver(the default since Python 3.14) so we catch issues like #4469 before release. This PR makesforkserverthe default for the tests on Linux, locally and on the CI, while users keepfork.Note that we make our own tests run on
forkserverlocally. This is important for us to catch errors. Your normal execution code locally will keep running withforkthough and you can still run the tests withforkusingpytest --mp-context=fork.