gh-119727: Run tests in parallel by default#120456
Closed
Uh oh!
There was an error while loading. Please reload this page.
Conversation
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
The Python test runner (regrtest) now runs tests in parallel by default. Use the --single-process option to run tests sequentially in a single process.
MemberAuthor
vstinner commented Jun 13, 2024
Fixing test_regrtest is more complicated than expected. I prefer to abandon this change for now. |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
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.
The Python test runner (regrtest) now runs tests in parallel by default. Use the --single-process option to run tests sequentially in a single process.
--single-processoption to regrtest to always run tests sequentially (ignore-jNoption) #119727