ci(fleet): serialize the remainder lane to lower peak hosted-runner demand - #544
Merged
Merged
Conversation
…emand The fleet fans out to twelve example repos, each dispatching several child runs that each need a GitHub hosted runner, and under that peak demand GitHub intermittently fails to allocate runners and cancels lanes. The retry coverage tolerates it; this reduces the cause. Drop the remainder lane max-parallel from two to one so the eight light repos run one at a time instead of two, roughly halving the peak concurrent runner demand during that lane. The remainder lane's wall-clock roughly doubles; total fleet wall-clock grows by less than that since the other lanes are unchanged. Lane sequencing, roster, needs-graph, the aggregate gate, and the retry attempts are unchanged. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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
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.
What
Reduce the CAUSE of the hosted-runner-starvation flake (rather than only tolerate it via retries, #543). The fleet fans out to 12 example repos, each dispatching several child runs that each need a GitHub hosted runner; under that peak, GitHub intermittently fails to allocate runners and cancels lanes.
Drop the
remainderlanemax-parallelfrom 2 to 1, so the 8 light repos run one at a time instead of two. This roughly halves the peak concurrent runner demand during that lane.Trade-off
The remainder lane's wall-clock roughly doubles; total fleet wall-clock grows by less than that (primary/dependents/heavy unchanged). Lane sequencing, roster, needs-graph, the aggregate gate, and
retry-attempts: 2are all unchanged. Together with #543's retries, the fleet now both reduces and tolerates the flake.Verification
actionlint clean;
go build,go test ./internal/release/...(170, includes fleet wiring checks - no test pins max-parallel),golangci-lintclean.