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

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

@@ -117,3 +117,12 @@ This file stores run-specific examples only when a run produced a new learning r
- Use one consistent ATVM status layout for all automation status responses.
- Keep the order the same: build name, completed machines, notes, skipped machines, remaining machines, summary, timing, estimated completion time.
- Keep machine entries one per line as `machine-name - STATUS` regardless of test type.
## Run Learning: 2026-03-13 (Put longer failure description on failed machine line)
- Observed requirement:
- Failed machines are easier to scan when the failure description appears directly on the same line as the machine status.
- A longer same-line description works better than a very short label when the extra detail helps explain what actually failed.
- Action for future runs:
- Format failed machine lines as `machine-name - FAIL - <failure description>`.
- Prefer the longer same-line description when it adds useful operator-facing context.
- Keep `Notes` for broader context, anomalies, and extra follow-up detail beyond the machine-specific failure description.