CI: when an acceptance check fails, print the serial log around it #136

Open
opened 2026-11-07 20:15:19 +00:00 by rajames · 0 comments
Owner

Found

Acceptance run 197 failed one riscv64 check (#131); the serial log that would explain it is only in the run's logs artifact, which Gitea's API does not list -- reading it takes the web UI.

Done when

  • scripts/qemu_session.py prints, on any FAIL, the serial lines around where the expected line belongs (e.g. 20 lines after "Boot successful!"), into the job's output
  • Verified with a deliberately failing check

🤖 Filed with Claude Code -- the review after v4.0.0-alpha.3 (Captain Bob, 2026-11-07: "a list of problems, deficiencies, smells and so on placed in issues by rank priority").

### Found Acceptance run 197 failed one riscv64 check (#131); the serial log that would explain it is only in the run's `logs` artifact, which Gitea's API does not list -- reading it takes the web UI. ### Done when - [ ] `scripts/qemu_session.py` prints, on any FAIL, the serial lines around where the expected line belongs (e.g. 20 lines after "Boot successful!"), into the job's output - [ ] Verified with a deliberately failing check 🤖 Filed with [Claude Code](https://claude.com/claude-code) -- the review after v4.0.0-alpha.3 (Captain Bob, 2026-11-07: "a list of problems, deficiencies, smells and so on placed in issues by rank priority").
rajames added this to the v4.0.0-alpha.4 milestone 2026-11-07 20:15:19 +00:00
rajames added the
priority
should
kind
feature
kind
ci
status
backlog
labels 2026-11-07 20:15:20 +00:00
Sign in to join this conversation.