Add CI job to run tests sequentially #133556
Draft
+65
−10
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
|
Thanks for this! Will take another look after the beta is out :)
Yeah, maybe. The current slowest job is free-threaded Windows at about 25m, so this new one would become the slowest. And hopefully we can improve the Windows one too. |
…_fast_cycle_creation
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.
Add a CI job to run all tests sequentially. This takes ~30m, so might be better as a buildbot worker?
Open questions:
release-toolscheck should we make this? Currently I've mirrored it quite closely, but we probably ought to be closer to the other common test configurations.maketarget for sequential testing?A