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

Remove verbose scope text from ATVM coverage

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 17:40:32 -04:00
parent 5432240525
commit 708eddd7fa
4 changed files with 2 additions and 3 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 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. - 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. - The `HOSTS:` table includes `Host`, `Kernel`, `Status`, and `Detail` columns in that order.
- 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 `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 or include verbose prose scope descriptions.
- In `TEST FLOW:`, show the template-specific 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. - 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`. - `cmc-e2e` currently uses the 22-step migration flow documented in `/home/aw/code/cds/atvm/docs/automation/status-template.md`.

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

@@ -310,6 +310,7 @@ This file stores run-specific examples only when a run produced a new learning r
- Include the ATVM config filename in `COVERAGE:`. - Include the ATVM config filename in `COVERAGE:`.
- Include important operator-relevant run options such as `--ignore_force_shutdown` 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. - Keep `COVERAGE:` focused on run intent and options, not the explicit target-host list.
- Do not include verbose prose lines such as `scope of this run: ...` in `COVERAGE:`.
## Run Learning: 2026-03-27 (Do not auto-add blacklist excludes for explicitly specified VMs) ## Run Learning: 2026-03-27 (Do not auto-add blacklist excludes for explicitly specified VMs)
- Observed requirement: - Observed requirement:

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

@@ -46,7 +46,6 @@ Use this as the default ATVM automation run-status template for:
- migration style: `<high-level test style>` - migration style: `<high-level test style>`
- integration/plugin path: `<integration/plugin>` - integration/plugin path: `<integration/plugin>`
- run options: `<operator-relevant options such as --ignore_force_shutdown>` - run options: `<operator-relevant options such as --ignore_force_shutdown>`
- scope of this run: `<batch or run scope>`
**TEST FLOW:** **TEST FLOW:**
- <template-specific numbered steps> - <template-specific numbered steps>

1
atvm/watcher-service/atvm_run_watcher.py
View File

@@ -804,7 +804,6 @@ def build_status_markdown(
f"- migration style: {metadata['migration_style']}", f"- migration style: {metadata['migration_style']}",
f"- integration/plugin path: `{metadata['integration_plugin']}`", f"- integration/plugin path: `{metadata['integration_plugin']}`",
f"- run options: {', '.join(f'`{value}`' for value in metadata.get('extra_options', [])) or 'none'}", f"- run options: {', '.join(f'`{value}`' for value in metadata.get('extra_options', [])) or 'none'}",
f"- scope of this run: {metadata['scope_description']}",
"", "",
"**TEST FLOW:**", "**TEST FLOW:**",
*test_flow_lines, *test_flow_lines,