Parallelize CLI tests #14339
Merged
Parallelize CLI tests #14339
Conversation
This file contains 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
matheusaaguiar
approved these changes
Jun 21, 2023
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.
This PR takes advantage of the recent improvements to the CLI test runner (#14289, #14338) to single out several particularly long CLI tests and run them in parallel. This makes the
_clijobs finish 2x faster.Bigger savings are possible, but with a lot more effort to make test selection more granular. Especially
~ast_import_exporttakes half of the running time and is currently a single test. Once we have better granularity we could also use CircleCI's time-based splitting, but that requires further changes - we'd need to generate JUnit-style XML reports. I'm not doing all that here. The goal of this PR is just to pick the low-hanging fruit while parallelizing the bytecode comparison tests (#14330) to prevent the byte comparison jobs from taking excessively long time in CI after #13583.