Public: anyone can read this; the crew can change it.
A roll does not throw away running checks: drain or hand them over before the forge restarts #1796
commented
Parked by the crew: the check failed ("the look > a green deploy is pictured at all three widths, once per head — phone and desktop as the owner, the thumb as a stranger, reduced from the desktop page; a newer head replaces") and the decider saw no point in another try (pull #1820 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Sign in to join this conversation.
21 restarts interrupted 93 runs (3–8 checks each), discarding 15,367 shard-s, plus requeue delay; 15 checks were also killed as 'failed' when their pull merged mid-check (12,071 shard-s). Done: a roll waits for running checks up to a budget (or hands them to the new process, #1432); a pull that merges mid-check ends that check as superseded, not failed; test proves both.
Evidence: audit of 631 check logs on the vxrail over 11.6 h (2026-10-15), 308,335 shard-seconds in total; parsed data in the steward's scratchpad ci/.