mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-11 21:26:44 +00:00
29 lines
1.6 KiB
Markdown
29 lines
1.6 KiB
Markdown
[Back to AGENTS hub](../../AGENTS.md)
|
|
|
|
# Debugging
|
|
|
|
Use the failure source to decide how to debug:
|
|
|
|
- If the failure happened during a local deploy, debug from the live local output and local logs.
|
|
- If the failure comes from GitHub, follow [CONTRIBUTING.md](../../CONTRIBUTING.md) and work from the downloaded `*job-logs.txt` or `*.log` files.
|
|
- If a run is still progressing and the user has not asked you to change course, wait for the long-running run to finish instead of interrupting it.
|
|
|
|
## Local Deploy Failures
|
|
|
|
- On the first local deploy failure, rerun the affected app with `APP=<role> make test-local-dedicated`. For alarm failures, use this retry path because it rebuilds the full `servers.yml` inventory in the dedicated shape.
|
|
- If the inventory is already in the right shape and you only need a faster repeat, use `APP=<role> make test-local-rapid`.
|
|
- Do not switch back to `APP=<role> make test-local-app` for the retry if you suspect inventory drift, because that follows the single-app inventory path.
|
|
- Keep iterating locally until the issue is fixed, unless the user explicitly asks you to switch context.
|
|
|
|
## GitHub / CI Logs
|
|
|
|
- Inspect relevant logs in `*job-logs.txt` or `*.log`.
|
|
- Treat the downloaded GitHub logs as the source of truth for CI failures.
|
|
|
|
### Playwright Failures
|
|
|
|
- If `*job-logs.txt` shows a Playwright failure, download the matching Playwright assets before you continue.
|
|
- Save the downloaded Playwright assets in `/tmp/` and keep them there.
|
|
- Output the storage path for the downloaded Playwright assets file.
|
|
- Analyze the downloaded Playwright assets together with `*job-logs.txt`.
|