Update ATVM status reporting to use longer inline failure descriptions
- 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:
@@ -124,7 +124,8 @@ Status details:
|
||||
- Show in-progress machines under remaining machines as `RUNNING`.
|
||||
- Show not-yet-started machines as `NOT STARTED`.
|
||||
- Use completed spec results already recorded in the log to determine machine pass/fail state.
|
||||
- For failed machines, mark the machine `FAIL` in the completed list and include the failure reason in `Notes`.
|
||||
- For failed machines, mark the machine `FAIL` in the completed list and append a longer failure description on the same machine line when the reason materially helps the operator understand the failure.
|
||||
- Keep `Notes` for broader context, anomalies, or follow-up details that are not part of the machine-specific failure description.
|
||||
- Include start time in status output when it can be derived from the log.
|
||||
- Include end time and total runtime for completed runs, or elapsed runtime for active runs.
|
||||
- Include quickest completed test runtime, longest completed test runtime, and average completed test runtime under timing details when they can be derived from the log.
|
||||
|
||||
Reference in New Issue
Block a user