A round that CI failed shows a green ✓, its judge reads only "lanes failed", and the skip row is a bare step.skipp… #179

Closed
opened 2026-10-16 18:34:44 -04:00 by cmoriarty · 1 comment
Owner

Seen on run 67 (production 74e261c), 2026-10-16. In rounds 1 and 2 the local lanes passed, but CI failed CI / Unit tests.

  • The check step shows a green ✓. script.run-tests and script.run-tests.r2 read ✓, because the step succeeded at running the checks, even though the round is red. Nothing on the spine says the round failed.
  • The judge's skip reads only its note. agent.judge.r2 shows lanes failed, its event's note. Its reason says what happened ("the fix loop's next step is fix in round 2: CI's job CI / Unit tests (push) failed at step Unit tests"), but the spine doesn't show it. CI being a "lane" isn't obvious to a person.
  • The transcript draws the skip as step.skipp…. The row is the event's type with the reason beside it, a not_needed skip with condition: judge_due. That case isn't covered by #175's wording.

Wanted

  • A check step whose round failed reads as failed: its row says the round is red and names the failing lane or job, e.g. round 2 red: CI / Unit tests (push).
  • The judge's skip says why in words, e.g. skipped: round 2 failed in CI (CI / Unit tests), so it is fixed before it is judged.
  • No transcript row shows step.skipped.
Seen on run 67 (production 74e261c), 2026-10-16. In rounds 1 and 2 the local lanes passed, but CI failed `CI / Unit tests`. - **The check step shows a green ✓.** `script.run-tests` and `script.run-tests.r2` read ✓, because the step succeeded at running the checks, even though the round is red. Nothing on the spine says the round failed. - **The judge's skip reads only its note.** `agent.judge.r2` shows `lanes failed`, its event's `note`. Its `reason` says what happened ("the fix loop's next step is fix in round 2: CI's job `CI / Unit tests (push)` failed at step `Unit tests`"), but the spine doesn't show it. CI being a "lane" isn't obvious to a person. - **The transcript draws the skip as `step.skipp…`.** The row is the event's type with the reason beside it, a `not_needed` skip with `condition: judge_due`. That case isn't covered by #175's wording. **Wanted** - A check step whose round failed reads as failed: its row says the round is red and names the failing lane or job, e.g. `round 2 red: CI / Unit tests (push)`. - The judge's skip says why in words, e.g. `skipped: round 2 failed in CI (CI / Unit tests), so it is fixed before it is judged`. - No transcript row shows `step.skipped`.
Author
Owner

Shipped in 55f376c (change a-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).

  • A fix loop check records its round's verdict on its row (schema 13): passed or failed, a few words naming what failed, and the round's problem.
  • The spine draws a red round as ✗, with its note on a line of its own under the row and its problem in the hover.
  • The loop's note says "CI failed" when only CI is red. The skip's reason starts with the round and what comes next.
  • A put-back ends the transcript's fold, and a skip's reason wraps on a line of its own under the row.
  • osfd transcript and the notifications read skips as the console does.
  • Checked on production in the run. Round 1's unit lane failed. script.run-tests read 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 before 74e261c. #181 now offers a reload when a new build is live. Closing.

Shipped in 55f376c (change `a-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). - A fix loop check records its round's verdict on its row (schema 13): passed or failed, a few words naming what failed, and the round's problem. - The spine draws a red round as ✗, with its note on a line of its own under the row and its problem in the hover. - The loop's note says "CI failed" when only CI is red. The skip's reason starts with the round and what comes next. - A put-back ends the transcript's fold, and a skip's reason wraps on a line of its own under the row. - `osfd transcript` and the notifications read skips as the console does. - Checked on production in the run. Round 1's unit lane failed. `script.run-tests` read 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 before 74e261c. #181 now offers a reload when a new build is live. Closing.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#179
No description provided.