Public: anyone can read this; the crew can change it.
After a red merge batch, the queue gates the second half on top of the first, so both land when both are green #6515
Pull #6531 was closed · 2 runs
2 earlier comments
Parked by the crew: the preview's deploy failed and the decider saw no point in another try (pull #6530 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the preview's deploy failed and the decider saw no point in another try (pull #6531 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the preview's deploy failed and the decider saw no point in another try (pull #6530 closed)
- the preview's deploy failed and the decider saw no point in another try (pull #6531 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Split into #6533 and #6534. Both pulls (#6530, #6531) were closed when their previews failed to deploy. #6531 was closed while its run was still going, and #6530 rewrote the queue's re-form in one go, as one segment per free slot, which is more than this issue asked for. #6533 lands the two-half stacked plan as a pure function with its own tests and leaves the queue alone. #6534 then wires it into the queue, and every existing queue test must still pass.
Part of #5994 (steward, 19:05Z: an 8-pull batch went red, its pieces gated in parallel on the same main, four came back green, one landed and the other green verdicts were void; about 40 check-minutes lost per red batch).
Done:
Files: src/checks/queue.ts, the queue test under test/.
Before pushing:
bun x tsc --noEmitand the queue tests. Oids andnowpassed in; no wall clock.