Public: anyone can read this; the crew can change it.
One green result per commit: a check on a commit already proven green is skipped, and a land does not re-run fast on a moved base #1795
the crew's run was interrupted: restart, resumes on the next pass — cancelled
commented
Parked by the crew: the check failed ("the next check honours a concurrency the admin lowered, and gets the shard count > lowered to one, three repositories' checks run one at a time; each sees FORGE_CHECK_SHARDS") and the decider saw no point in another try (pull #1835 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.
The final heads of 197 pulls got 328 runs (131 extra); 50 runs repeated an exact head+base; 21 main commits were gated 38 times, 11 with two passing gates minutes apart (~9k shard-s). Done: checks are keyed by (head, base, gate manifest); an identical key reuses the verdict; the landing gate runs once per commit; test proves a re-request returns the cached verdict.
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/.