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

Expand ATVM coverage details with run options

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 17:32:22 -04:00
parent 9024d5cadb
commit 5432240525
5 changed files with 40 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -241,7 +241,7 @@ Status-report expectations:
- Do not include generic watcher bookkeeping messages in `NOTES:` such as artifact-detection confirmations.
- Do not include internal watcher fallback notes in `NOTES:` such as `check-xml-files.ts` validation confirmations or reporter-artifact recovery details.
- 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 `COVERAGE:`, describe the template, datastore/config family, config filename, migration style, plugin/integration path, and other operator-relevant run options, but do not list target hosts there.
- 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 22-step migration flow documented in `/home/aw/code/cds/atvm/docs/automation/status-template.md`.

10
atvm/docs/automation/run-learnings.md
View File

@@ -301,6 +301,16 @@ This file stores run-specific examples only when a run produced a new learning r
- Treat `approve` as approval to run and start the watcher.
- Treat `approve without watcher` as approval to run without starting the watcher.
## Run Learning: 2026-03-27 (Expand coverage details with operator-relevant run options)
- Observed requirement:
- The operator wants `COVERAGE:` to include more than template and datastore family.
- Useful additions include the config filename and important flags such as `--ignore_force_shutdown`.
- Explicit VM names do not need to be repeated there because the host listing already shows them.
- Action for future runs:
- Include the ATVM config filename in `COVERAGE:`.
- Include important operator-relevant run options such as `--ignore_force_shutdown` in `COVERAGE:`.
- Keep `COVERAGE:` focused on run intent and options, not the explicit target-host list.
## Run Learning: 2026-03-27 (Do not auto-add blacklist excludes for explicitly specified VMs)
- Observed requirement:
- When the operator explicitly specifies the VM or VM list to run, they do not want the maintained `--exclude_partial_match` blacklist added automatically.

3
atvm/docs/automation/status-template.md
View File

@@ -42,8 +42,10 @@ Use this as the default ATVM automation run-status template for:
**COVERAGE:**
- template: `<template-name>`
- datastore/config family: `<config family>`
- config file: `<config-file-name>`
- migration style: `<high-level test style>`
- integration/plugin path: `<integration/plugin>`
- run options: `<operator-relevant options such as --ignore_force_shutdown>`
- scope of this run: `<batch or run scope>`
**TEST FLOW:**
@@ -76,6 +78,7 @@ Use this as the default ATVM automation run-status template for:
- Do not include generic watcher bookkeeping lines in `NOTES:` such as "run artifacts were detected" or "final reporting artifacts were detected."
- Do not include internal fallback notes in `NOTES:` such as "`check-xml-files.ts` validation passed" or "host details were derived from reporter artifacts."
- `COVERAGE:` should describe what the run was intended to cover without listing target hosts.
- `COVERAGE:` should also include operator-relevant run options such as the config filename and important flags like `--ignore_force_shutdown`.
- `TEST FLOW:` should describe the template-specific numbered run flow once for the whole test, not per host.
- The watcher resolves `TEST FLOW:` from the run template name.
- `cmc-e2e` currently uses this flow: