The fix loop can't see why CI failed #249
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?
What happens
In run 120, CI failed at
npx playwright install --chromium --with-deps:--chromiumisn'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_evidenceinsrc/osf/forgejo.py, andjob_stepsinsrc/osf/pipeline/cilane.py. Related: #248.From the Braid vs Claude Code pinball test, 2026-10-27 (runs 110–120).
What shipped
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.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 witherror: unknown option '--chromium'.Shipped in
5598ddf(OpenSpec changereliable-dispatch-merge-and-ci-evidence, archived).