From 708eddd7fa91d54f559e6ece0380a87fcc48c62c Mon Sep 17 00:00:00 2001 From: "anthony.wen" Date: Fri, 27 Mar 2026 17:40:32 -0400 Subject: [PATCH] Remove verbose scope text from ATVM coverage --- atvm/docs/automation/guide.md | 2 +- atvm/docs/automation/run-learnings.md | 1 + atvm/docs/automation/status-template.md | 1 - atvm/watcher-service/atvm_run_watcher.py | 1 - 4 files changed, 2 insertions(+), 3 deletions(-) diff --git a/atvm/docs/automation/guide.md b/atvm/docs/automation/guide.md index aad6019..ce14258 100644 --- a/atvm/docs/automation/guide.md +++ b/atvm/docs/automation/guide.md @@ -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, 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. - 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`. diff --git a/atvm/docs/automation/run-learnings.md b/atvm/docs/automation/run-learnings.md index 38f2730..be837d7 100644 --- a/atvm/docs/automation/run-learnings.md +++ b/atvm/docs/automation/run-learnings.md @@ -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 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. + - 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) - Observed requirement: diff --git a/atvm/docs/automation/status-template.md b/atvm/docs/automation/status-template.md index b02dfee..b63d4e2 100644 --- a/atvm/docs/automation/status-template.md +++ b/atvm/docs/automation/status-template.md @@ -46,7 +46,6 @@ Use this as the default ATVM automation run-status template for: - migration style: `` - integration/plugin path: `` - run options: `` -- scope of this run: `` **TEST FLOW:** - diff --git a/atvm/watcher-service/atvm_run_watcher.py b/atvm/watcher-service/atvm_run_watcher.py index 6bded60..348a4a4 100644 --- a/atvm/watcher-service/atvm_run_watcher.py +++ b/atvm/watcher-service/atvm_run_watcher.py @@ -804,7 +804,6 @@ def build_status_markdown( f"- migration style: {metadata['migration_style']}", f"- integration/plugin path: `{metadata['integration_plugin']}`", 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_lines,