feat(gitea-mq): raise the batch cap to twenty for flake-update waves - #3014
Merged
Conversation
The five-entry cap matched Mic92/dotfiles, SBEE-Lab/infra and mulatta/dots. Two conditions those deployments do not share justify diverging: our update-flake-inputs lane produces waves of twenty to forty simultaneously ready PRs twice weekly, and bisectMaxSteps = 0 makes bisection unlimited, so Engine.HandleFail isolates a failing entry in about log2(N) builds and the eject-the-whole-batch path is unreachable here. Accepted trade: a large batch holds the queue for one build cycle, and one bad entry delays the other nineteen while bisection runs. The cap is a ceiling, not a target. FormBatch is greedy, taking whatever is queued when a poll runs, and a pull_request event triggers that poll immediately, so batch size stays emergent from arrival rate against build time. Observed here: five PRs landed in two batches of two and three. No speedup beyond that observation is claimed. design.md records the reversal with both reasons; brainstorm.md keeps the earlier zero-to-five decision untouched as the historical record. Change-Id: Ifc76b011fd3b7a8361469c693da847db6a6a6964
Owner
Author
|
This pull request is part of a Mergify stack:
|
cameronraysmith
added this pull request to stack #3016
September 10, 2026 04:15
sciexp-gitea-mq
Bot
deleted the
stack/cameronraysmith/stack/queue-cutover/raise-batch-cap-twenty-flake-update-waves--fc76b011
branch
September 10, 2026 04:27
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.
The five-entry cap matched Mic92/dotfiles, SBEE-Lab/infra and mulatta/dots.
Two conditions those deployments do not share justify diverging: our
update-flake-inputs lane produces waves of twenty to forty simultaneously
ready PRs twice weekly, and bisectMaxSteps = 0 makes bisection unlimited, so
Engine.HandleFail isolates a failing entry in about log2(N) builds and the
eject-the-whole-batch path is unreachable here.
Accepted trade: a large batch holds the queue for one build cycle, and one bad
entry delays the other nineteen while bisection runs.
The cap is a ceiling, not a target. FormBatch is greedy, taking whatever is
queued when a poll runs, and a pull_request event triggers that poll
immediately, so batch size stays emergent from arrival rate against build
time. Observed here: five PRs landed in two batches of two and three. No
speedup beyond that observation is claimed.
design.md records the reversal with both reasons; brainstorm.md keeps the
earlier zero-to-five decision untouched as the historical record.