Files
computer-playbook/docs/agents/action/debug/log.md
kevinveenbirkenbachandClaude Opus 4.8 9c029870fe feat(cli): add CI-logs download and analyze tooling
python -m cli.meta.ci.logs.download fetches a run's job logs and artefacts in parallel, with conclusion filters (-s/-f/-c/-k), a jobs.json/summary.tsv manifest, per-request jitter to dodge API rate limits, and idempotent re-runs. python -m cli.meta.ci.logs.analyze clusters the downloaded logs by their root failing task.

Rename the agent CI-triage page debug/pipeline.md to debug/ci.md, point its download/inspect step at the new CLI, and reference the tooling from the contributing CI-debugging page. Add unit tests for both commands.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-26 17:01:08 +02:00

7 lines
428 B
Markdown

# Log File Inspection
Use this page when the operator has manually placed `*.log` or `*job-logs.txt` files in the repository workdir for ad-hoc inspection. For the fully automated CI triage that fetches logs itself via `gh`, see [ci.md](ci.md).
- You MUST inspect the relevant logs in the provided `*job-logs.txt` or `*.log` files.
- You MUST treat the provided log files as the source of truth for the failure they describe.