Repository navigation
Conversation
The fleet has grown from 12 legs to 82 while the cap stayed at 5, so it alone takes 42-87 minutes and is the last job to finish on full runs; the production deploy waits on it. 12 of the plan's 20 hosted slots leaves 8 for the rest of the run and sibling workflows.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
blove
marked this pull request as ready for review
November 16, 2026 00:26
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 16, 2026
This branch was successfully deployed
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
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
cockpit-e2estrategy.max-parallel5 → 12, and the guard assertion on that value inscripts/ci-workflow.spec.mjs. No job, step, test, gate,needsedge, cache or permission changes.Why
The cap was chosen when the fleet had 12 legs. It now has 82 at about 2.5 minutes each, so 5 wide has a floor near 40 minutes. In ten sampled runs the fleet took 42–87 minutes on full-fleet runs and was the last job to finish;
CI — requiredandDeploy → Vercelboth wait on it. The organization plan allows 20 concurrent hosted jobs, and the sampled runs peaked at exactly 20.Expected effect (simulated, not yet measured)
Replaying recorded job durations at width 12 ends a full-fleet run about 20–26 minutes sooner with unchanged compute. That is a best case for a run with the pool to itself. With several runs overlapping the gain shrinks and non-fleet jobs finish later, though each run as a whole still ends sooner in every scenario replayed.
This PR is the measurement: it changes
ci.yml, so it runs the full fleet with the same-run dependency artifact, comparable to recent merge-queue and main runs.Verified locally
node --test scripts/ci-workflow.spec.mjs: 201 pass (fails5 !== 12when only the spec is changed)scripts/cockpit-matrix.spec.mjs48 pass,scripts/cockpit-dependencies.spec.mjs37 passAggregate matrix outcomeandVerify scoped CI jobsscripts, run with failed / cancelled / skipped / empty / malformed fleet results, deny each oneNot verified locally:
scripts/ci-scope.spec.mjsdid not finish on my machine; the diff does not touch the classifier.Risks
Rollback
Revert this commit.
🤖 Generated with Claude Code