A failed CI job's log reaches the fix round as the job's tail, mostly post-step cleanup: the error itself is cut to one line #180
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. The CI lane (#163) gives a failed job's log to the fix round as the last 3,000 characters of the job's log. That tail is almost all the job's post steps: "⭐ Run Post Check out the repository", the git config cleanup, "✅ Success - Post Check out the repository".The failure itself survives only as a cut line at the very top:
ts,line=227,column=3::Error: Test timed out in 5000ms. … ❯ test/server.test.ts:227:3.…: undefined, … file: 'pg_type.c', routine: 'TypeCreate' }. That's a Postgres error whose message and test name were cut off; most likely concurrentCREATE TABLEin CI's shared database.So the fix round works half blind on exactly the failures it can't see locally, which makes more rounds, and more cap failures (#178), likely.
Wanted
Unit tests"), up to its end. Post steps and the job's set-up are left out.::error, the test runner's summary), keep those whole even when the tail is cut.Shipped in
bb5d87a(changeci-log-is-the-failing-step, commit609debb), live since 00:07Z on 2026-10-17, and archived after the verification run (run_01M53R7621CJW6PCZG7S6R94HS, thorough on cmoriarty/braid-combined-test, vLLM, succeeded and merged at 03:49Z).exitcode '1': failureline, so it ends where the failing step ended, not after the post steps.::errorannotation, which names the failing test, its file and line, and its message, is kept whole and decoded at the top.Closing; the next run whose CI fails will show it.