anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Recover watcher results when run log is missing

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 11:00:11 -04:00
parent 4c0e28cc05
commit cc551a6922
2 changed files with 74 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
atvm/docs/automation/run-learnings.md
View File

@@ -230,3 +230,13 @@ This file stores run-specific examples only when a run produced a new learning r
- When the watcher is approved, start the watcher before `run-sorry-cypress.py`.
- Keep the order as: template generation, verification, watcher start, runner start.
- Do not launch the runner first when the watcher is part of the approved command set.
## Run Learning: 2026-03-27 (Watcher must recover when the consolidated run log is missing)
- Observed failure mode:
- A non-categorized watcher run can finish without posting Mattermost even when the ATVM test itself passed.
- In this case the watcher service expected `/tmp/<build-name>.log`, but that consolidated run log was never written.
- The run still produced the final `check-xml-files.ts` XML and fresh per-host reporter artifacts under `cmcReporter/logs/<host>/`.
- Action for future runs:
- Do not rely only on `/tmp/<build-name>.log` for non-categorized watcher result recovery.
- When final `check-xml-files.ts` validation is present but host XML is absent, recover host completion from the latest matching per-host reporter artifact within the run window.
- Keep non-categorized watcher notes accurate; do not describe that failure as a categorized sub-run issue.