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

atvm: resolve automation status from local workflow artifacts

Browse Source 
Clarify that ATVM automation status requests refer to the local atvm
folder workflow and the automation VM at 192.168.3.190, not Cirrus
project operations such as the atvm - cypress project.

Update the ATVM guide and AGENTS notes to prefer local evidence in this
order when reporting status:
- active runner processes
- live automation VM files
- shell history for the last launch command
- historical reporter artifacts

Record the new run learning in atvm-automation-runs.md so future status
requests use the correct source of truth.
This commit is contained in:
anthony.wen
2026-03-18 08:22:24 -04:00
parent 8d2e245c6b
commit 51d782d964
3 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
atvm/atvm-automation-runs.md
View File

@@ -154,3 +154,13 @@ This file stores run-specific examples only when a run produced a new learning r
- Add `--ignore_force_shutdown` to every `cmc-templates.py` command unless the operator explicitly asks not to use it.
- Default plugin-bearing ATVM automation commands to `--use_specified_plugin iscsi`.
- Only switch away from `iscsi` when the operator explicitly requests `fc`, `both`, or another applicable override.
## Run Learning: 2026-03-18 (ATVM status requests must resolve from the local ATVM workflow, not Cirrus project operations)
- Observed failure mode:
- Interpreting "status of the ATVM automation run" as a request about Cirrus project operations can return the wrong source entirely.
- The operator uses "ATVM automation" to mean the automation contained in the local `atvm` folder and the corresponding automation VM workflow.
- Action for future runs:
- Resolve ATVM status requests from the local ATVM workflow first.
- Check the automation VM at `192.168.3.190` for live runner processes and live files before looking at historical artifacts.
- If no automation is active, reconstruct the most recent historical run from the automation VM shell history and reporter artifacts.
- Do not use Cirrus project operations such as `atvm - cypress` as the source for ATVM automation status unless the operator explicitly asks for project-operation status.