A round that CI failed shows a green ✓, its judge reads only "lanes failed", and the skip row is a bare step.skipp… #179
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Seen on run 67 (production
74e261c), 2026-10-16. In rounds 1 and 2 the local lanes passed, but CI failedCI / Unit tests.script.run-testsandscript.run-tests.r2read ✓, because the step succeeded at running the checks, even though the round is red. Nothing on the spine says the round failed.agent.judge.r2showslanes failed, its event'snote. Itsreasonsays what happened ("the fix loop's next step is fix in round 2: CI's jobCI / Unit tests (push)failed at stepUnit tests"), but the spine doesn't show it. CI being a "lane" isn't obvious to a person.step.skipp…. The row is the event's type with the reason beside it, anot_neededskip withcondition: judge_due. That case isn't covered by #175's wording.Wanted
round 2 red: CI / Unit tests (push).skipped: round 2 failed in CI (CI / Unit tests), so it is fixed before it is judged.step.skipped.step.skipped: <label>and never says the step was put back #175Shipped in
55f376c(changea-red-round-reads-red), live since 23:32Z on 2026-10-16, and archived after the verification run (run_01M53R7621CJW6PCZG7S6R94HS, thorough on cmoriarty/braid-combined-test, vLLM, succeeded and merged at 03:49Z).osfd transcriptand the notifications read skips as the console does.script.run-testsread verdict failed, "round 1 red: unit lane".agent.judge's skip read "lanes failed", with "round 1: lanes failed, so it is fixed before it is judged: the unit lane failed: the suite exited 1". Round 2's check read "round 2 green".The
step.skipp…in your screenshot was a console tab still on the build before74e261c. #181 now offers a reload when a new build is live. Closing.