The fix loop can't see why CI failed #249

Closed
opened 2026-10-27 15:30:58 -04:00 by cmoriarty · 1 comment
Owner

What happens
In run 120, CI failed at npx playwright install --chromium --with-deps: --chromium isn't a valid option. The fixer never saw that error, because Forgejo returns 404 when Braid's token asks for a job log. CI failed twice, the fix in between couldn't help, and the run stopped to ask for help.

Fix
When there's no log, run the failed step's command locally and give its output to the fixer.

Done when
A CI failure reaches the fixer with the real error.

Where to look: job_evidence in src/osf/forgejo.py, and job_steps in src/osf/pipeline/cilane.py. Related: #248.

From the Braid vs Claude Code pinball test, 2026-10-27 (runs 110–120).

**What happens** In run 120, CI failed at `npx playwright install --chromium --with-deps`: `--chromium` isn't a valid option. The fixer never saw that error, because Forgejo returns 404 when Braid's token asks for a job log. CI failed twice, the fix in between couldn't help, and the run stopped to ask for help. **Fix** When there's no log, run the failed step's command locally and give its output to the fixer. **Done when** A CI failure reaches the fixer with the real error. Where to look: `job_evidence` in `src/osf/forgejo.py`, and `job_steps` in `src/osf/pipeline/cilane.py`. Related: #248. _From the Braid vs Claude Code pinball test, 2026-10-27 (runs 110–120)._
Author
Owner

What shipped

  • When Forgejo gives no log for a failed job, Braid runs the job's run: steps in the run's clone, in order, until one fails, and the red lane carries that step and its output, marked as Braid's own run.
  • Actions (uses:) and steps with expressions only CI fills in are skipped and named; a job with services is not run.

Test
tests/pipeline/test_ci_lane.py: run 120's install step comes back with error: unknown option '--chromium'.

Shipped in 5598ddf (OpenSpec change reliable-dispatch-merge-and-ci-evidence, archived).

**What shipped** - When Forgejo gives no log for a failed job, Braid runs the job's `run:` steps in the run's clone, in order, until one fails, and the red lane carries that step and its output, marked as Braid's own run. - Actions (`uses:`) and steps with expressions only CI fills in are skipped and named; a job with services is not run. **Test** `tests/pipeline/test_ci_lane.py`: run 120's install step comes back with `error: unknown option '--chromium'`. _Shipped in 5598ddf (OpenSpec change `reliable-dispatch-merge-and-ci-evidence`, archived)._
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#249
No description provided.