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

Show full template test flow in ATVM status

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 10:19:02 -04:00
parent 2699651f8f
commit 53f9e68fcd
4 changed files with 84 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -214,7 +214,7 @@ When asked for one VM or a VM set:
When the operator asks for the status of an ATVM automation run, report in this order:
1. Heading/title using the run `build_name`.
2. `COVERAGE:` section describing what the run was intended to cover, excluding the target-host list.
3. `TEST FLOW:` section describing the generic numbered run flow for the test.
3. `TEST FLOW:` section describing the template-specific numbered run flow for the test.
4. Completed machines with machine name first and status second for each machine.
5. Notes.
6. Skipped machines with reason.
@@ -235,7 +235,9 @@ Status-report expectations:
- The default ATVM status template uses flat bullet-list sections for `COVERAGE:` and `TEST FLOW:`, Markdown tables for `SUMMARY:`, `HOSTS:`, and `TIMING:`, and uses `NOTES:` for flat operator-facing notes.
- The `HOSTS:` table includes `Host`, `Kernel`, `Status`, and `Detail` columns in that order.
- In `COVERAGE:`, describe the template, datastore/config family, migration style, and plugin/integration path, but do not list target hosts there.
- In `TEST FLOW:`, show the generic numbered run flow once for the whole test, not per host.
- In `TEST FLOW:`, show the template-specific numbered run flow once for the whole test, not per host.
- Resolve the flow from the run template name.
- `cmc-e2e` currently uses the 18-step migration flow documented in `/home/aw/code/cds/atvm/docs/automation/status-template.md`.
- For the `Kernel` column, cross-reference the host name against `/home/aw/code/cds/atvm/inventory/vm-inventory.md`.
- If the hostname is not present in `vm-inventory.md`, report the kernel value as `unknown`.
- Treat references to the "ATVM automation run" or "automation run" as referring to this ATVM folder workflow and the automation VM at `192.168.3.190`, not to Cirrus project operations such as the `atvm - cypress` project.