Improve CI by matching variants to the number of workers#6017
Merged
Conversation
rnewson
approved these changes
May 29, 2026
Previously, after we added trixie we ended up with N+1 variants for N worker slots for generic docker workers. This means CI jobs have to wait until one of the workers finishes completely before even starting. To improve the situation, let's skip intermediate (27 currently) CI run to hopefully restore the speed back. There is some separate docker pull or java run flakiness we noticed but that's not related to this most likely.
nickva
force-pushed
the
fix-ci-reduce-run-count
branch
from
492e5ae to
9f71bfe
Compare
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.
Previously, after we added trixie we ended up with N+1 variants for N worker slots for generic docker workers. This means CI jobs have to wait until one of the workers finishes completely before even starting. To improve the situation, let's skip intermediate (27 currently) CI run to hopefully restore the speed back.
There is some separate docker pull or java run flakiness we noticed but that's not related to this most likely.