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

added more information to the printout when asking to give me status of the atvm automation run

Browse Source
This commit is contained in:
anthony.wen
2026-03-11 17:16:13 -04:00
parent 93b6d7acb8
commit 94d16c9536
3 changed files with 16 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
atvm/AGENTS.md
View File

@@ -96,7 +96,7 @@ Use `atvm-automation-examples.md` as the common options/command reference.
### Status Request Format ### Status Request Format
When the operator asks for run status, report in this order: When the operator asks for run status, report in this order:
1. Heading/title using the run `build_name`. 1. Heading/title using the run `build_name`.
2. Completed machines with pass/fail state for each machine. 2. Completed machines with machine name first and status second for each machine.
3. Skipped machines with reason. 3. Skipped machines with reason.
4. Remaining machines still to run. 4. Remaining machines still to run.
5. Summary counts for finished, passed, failed, and skipped machines. 5. Summary counts for finished, passed, failed, and skipped machines.
@@ -112,6 +112,7 @@ When the operator asks for run status, report in this order:
Status details: Status details:
- Use the live run log on the automation VM when available. - Use the live run log on the automation VM when available.
- Use the run `build_name` as the heading/title when available. - Use the run `build_name` as the heading/title when available.
- Format every machine entry as `machine-name - STATUS`.
- Show blacklisted machines under skipped machines when they are part of the requested scope. - Show blacklisted machines under skipped machines when they are part of the requested scope.
- Show in-progress machines under remaining machines as `RUNNING`. - Show in-progress machines under remaining machines as `RUNNING`.
- Show not-yet-started machines as `NOT STARTED`. - Show not-yet-started machines as `NOT STARTED`.
@@ -120,6 +121,7 @@ Status details:
- Include start time in status output when it can be derived from the log. - 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 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. - 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.
- Make the estimated completion time refer to the entire remaining run, not only the current machine/spec.
### Automation Blacklist ### Automation Blacklist
Always exclude these machines with `--exclude_partial_match` when building ATVM automation commands. Always exclude these machines with `--exclude_partial_match` when building ATVM automation commands.

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

@@ -133,7 +133,7 @@ When asked for one VM or a VM set:
## Status Reporting Format ## Status Reporting Format
When the operator asks for the status of an ATVM automation run, report in this order: When the operator asks for the status of an ATVM automation run, report in this order:
1. Heading/title using the run `build_name`. 1. Heading/title using the run `build_name`.
2. Completed machines with pass/fail state for each machine. 2. Completed machines with machine name first and status second for each machine.
3. Skipped machines with reason. 3. Skipped machines with reason.
4. Remaining machines still to run. 4. Remaining machines still to run.
5. Summary counts for finished, passed, failed, and skipped machines. 5. Summary counts for finished, passed, failed, and skipped machines.
@@ -149,6 +149,7 @@ When the operator asks for the status of an ATVM automation run, report in this
Status-report expectations: Status-report expectations:
- Use the live automation VM state when available. - Use the live automation VM state when available.
- Derive the heading/title from the run `build_name` when available. - Derive the heading/title from the run `build_name` when available.
- Format every machine entry as `machine-name - STATUS`.
- Derive completed-machine status from completed spec results already written to the run log. - Derive completed-machine status from completed spec results already written to the run log.
- Include the run start time in every status response when it can be derived from the run log. - Include the run start time in every status response when it can be derived from the run log.
- If the run is complete, include the end time and total run time. - If the run is complete, include the end time and total run time.
@@ -163,4 +164,5 @@ Status-report expectations:
- If a machine has not started yet, show it under remaining machines as `NOT STARTED`. - 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 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` and include the failure reason from the run log. - If a completed spec result shows a failure, report that machine as `FAIL` and include the failure reason from the run log.
- Base the completion estimate on the current remaining machine count and recent per-machine runtime visible in the run log. - 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.

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

@@ -45,3 +45,12 @@ This file stores run-specific examples only when a run produced a new learning r
- For failed machines in status responses, include the failure reason taken from the run log. - For failed machines in status responses, include the failure reason taken from the run log.
- Include timing details in status responses: start time, end time when complete, and total or elapsed runtime. - Include timing details in status responses: start time, end time when complete, and total or elapsed runtime.
- Also include timing stats in status responses: quickest completed test runtime, longest completed test runtime, and average completed test runtime. - Also include timing stats in status responses: quickest completed test runtime, longest completed test runtime, and average completed test runtime.
## Run Learning: 2026-03-11 (Machine-first status lines and whole-run ETA)
- Observed requirement:
- Status output must list each machine first and then its status, rather than leading with the status label.
- Estimated completion time must refer to the entire remaining automation run, not only the currently running machine.
- Action for future runs:
- Format machine entries as `machine-name - STATUS`.
- Keep failure reasons after the machine/status entry when a machine failed.
- When giving ETA, explicitly state it is the estimate for completion of the full remaining run.