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

Keep categorized ATVM watcher alive until parent run finishes

Browse Source 
- update the watcher to treat categorized parent-run activity as the authoritative signal for whether the overall request is still running
- prevent the watcher from exiting early just because one categorized grouped sub-run completed and wrote artifacts
- document that categorized watcher instances must remain alive between grouped runs until the parent request has actually gone inactive past the grace window
- update the ATVM guide, watcher design, and install docs to reflect the stricter categorized parent-run completion rule
This commit is contained in:
anthony.wen
2026-03-26 12:39:23 -04:00
parent 1ba508169f
commit 44e6e0e653
5 changed files with 23 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
atvm/docs/automation/guide.md
View File

@@ -45,6 +45,8 @@ Run ATVM CMC automation tests on the designated automation VM without unintended
- Treat `approve with watcher` as approval to run and also start the per-run watcher service for that build.
- When `--categorize` is used with watcher enabled, treat the watcher as a sequential grouped-run watcher:
- it must post one final Mattermost status per completed categorized group/sub-run
- it must stay active between grouped sub-runs while the parent categorized request is still running
- it must not stop after the first grouped run simply because one grouped run completed
- it must not wait and replace those with one single parent-only post
- After execution, report immediate success/failure only.
- Do not actively monitor completion unless explicitly requested.

2
atvm/docs/automation/mattermost-watcher-design.md
View File

@@ -42,6 +42,8 @@ A categorized run must be treated differently:
- the watcher must wait for that grouped sub-run to complete
- then send that grouped sub-run's final Mattermost status
- then continue watching for the next grouped sub-run
- the watcher must remain alive while the parent categorized request or related child Cypress process is still active
- one completed grouped sub-run must not be treated as proof that the parent categorized request is finished
- the watcher must not wait until the very end to send one single parent-only post
Evidence sources: