From bf1154441c53e542712ce6425c6409e624bae1c6 Mon Sep 17 00:00:00 2001 From: Cirrus Codex Date: Thu, 21 May 2026 07:57:11 -0400 Subject: [PATCH] Use single CMC kernel test results artifact --- tests/cmc-upgrade-kernel-test.md | 21 +++++---------------- 1 file changed, 5 insertions(+), 16 deletions(-) diff --git a/tests/cmc-upgrade-kernel-test.md b/tests/cmc-upgrade-kernel-test.md index 80c1531..c9002de 100644 --- a/tests/cmc-upgrade-kernel-test.md +++ b/tests/cmc-upgrade-kernel-test.md @@ -160,7 +160,7 @@ Validate CMC behavior across staged kernel upgrades on a cloned VM, including CM - [ ] 73. From vCenter, delete the cloned VM and its disks from inventory. - [ ] 74. Using Cirrus Data MCP tools, run final host cleanup for `skidamarink`, remove the cloned host entry for this test clone only, and verify the cloned host entry plus all migration sessions for the cloned host are gone. - [ ] 75. Blocker-fail path after clone creation, as an alternate to steps 71-74: leave the cloned VM powered on and present in inventory for manual inspection, then continue to step 76. -- [ ] 76. Append the current run to the summary and results files with the required host metadata, kernel progression, execution summary, final outcome, and total test duration; keep result artifacts under `tmp/` local-only and do not commit them. +- [ ] 76. Append the current run only to `/home/cirrus/cds/tmp/tests/cmc upgrade test/cmc-upgrade-kernel-test-results.md` with the required host metadata, kernel progression, execution summary, final outcome, and total test duration; do not create or update any other result, run-specific result, or summary files. ## Stop Conditions Stop immediately and record a blocker if any of these occur: @@ -246,24 +246,13 @@ Use one cumulative results file and append one new section per tested host. Keep ## Result Artifacts - Results file: `/home/cirrus/cds/tmp/tests/cmc upgrade test/cmc-upgrade-kernel-test-results.md` -- Summary file: `/home/cirrus/cds/tmp/tests/cmc upgrade test/cmc-upgrade-kernel-test-summary.md` +- The results file is the only run artifact to create or update. Do not create run-specific result files, summary files, or any other result files. - Result artifacts under `tmp/` are local run records only and must not be committed. -- Always append the latest run outcome to both files for `PASS`, `FAIL`, and `PARTIAL` outcomes. -- Do not leave a completed test run only in conversation; the artifact files are the source of record. +- Always append the latest run outcome to the results file for `PASS`, `FAIL`, and `PARTIAL` outcomes. +- Do not leave a completed test run only in conversation; the results file is the source of record. - All recorded timestamps must use UTC format: `YYYY-MM-DD HH:MM UTC`. - Record the UTC start time when the run begins. - Record the UTC end time when the run reaches a terminal outcome and the allowed final checklist actions for that outcome are complete. -- Compute `Test duration` from the recorded start/end timestamps and include it in both files. +- Compute `Test duration` from the recorded start/end timestamps and include it in the results file. - If a run is still in progress when first recorded, update the runtime once the run reaches its terminal outcome. - Use the `Per-Host Test Result Record` format for the results file. - -Summary file requirements: -- Start the file with the test file name line: `Test file: cmc-upgrade-kernel-test.md` -- Title: `CMC Upgrade Kernel Test Summary` -- Include test start time, test end time, and total test duration for the run -- Include a short run summary (current kernel -> first CMC install phase -> kernel upgrade -> CMC uninstall -> kernel upgrade -> second CMC install phase) -- Include host tested, kernel progression (start, step-up, latest), and overall result -- Include package metadata stale-view notes, candidate scope decisions, and final cloned-host/session cleanup status when present. -- Start each run section with a `##` heading that includes the OS family and the final outcome, for example: `## Amazon Linux 2023 - PASS`. -- Put the OS version and the rest of the run details under that heading so the heading stays the visible OS label above the test snippet. -- Backfill `Test duration` into the summary and results artifacts for any run where both timestamps are known.