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

Update ATVM status reporting to use longer inline failure descriptions

Browse Source 
- show failed machines with a longer failure description on the same status line

- keep Notes for broader context beyond the machine-specific failure reason

- update the ATVM automation guide and AGENTS rules to match

- record the reporting preference in atvm-automation-runs.md
This commit is contained in:
anthony.wen
2026-03-12 21:13:54 -04:00
parent ecae52712f
commit eb66f93432
3 changed files with 13 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
atvm/atvm-automation-guide.md
View File

@@ -182,6 +182,7 @@ Status-report expectations:
- If a machine is currently in progress, show it under remaining machines as `RUNNING`.
- If a machine has not started yet, show it under remaining machines as `NOT STARTED`.
- If no failures are present in completed spec results, report those completed machines as `PASS`.
- If a completed spec result shows a failure, report that machine as `FAIL` in the completed list and put the failure reason in `Notes`.
- If a completed spec result shows a failure, report that machine as `FAIL` in the completed list and append a longer same-line failure description when the extra detail is useful to the operator.
- Use `Notes` for extra context beyond the machine-specific same-line failure description.
- Base the completion estimate on the full remaining machine count and recent per-machine runtime visible in the run log.
- Make the estimate explicitly refer to completion of the entire remaining run, not only the current machine/spec.