Add detailed ATVM reboot test flow
This commit is contained in:
@@ -271,6 +271,14 @@ This file stores run-specific examples only when a run produced a new learning r
|
||||
- Action for future runs:
|
||||
- Render ATVM status output in that section order for both local output and Mattermost posts.
|
||||
|
||||
## Run Learning: 2026-03-30 (Give `cmc-reboot` a full template-specific test flow)
|
||||
- Observed failure mode:
|
||||
- `cmc-reboot` status output fell back to the generic 5-step placeholder flow.
|
||||
- The actual reboot workflow is substantially longer and includes reboot-specific validation around cmotion, revert cmotion, and post-reboot disk verification.
|
||||
- Action for future runs:
|
||||
- Define a dedicated `cmc-reboot` `TEST FLOW:` in the watcher and status template.
|
||||
- Keep the reboot flow aligned with the generated reboot Cypress spec rather than the generic fallback list.
|
||||
|
||||
## Run Learning: 2026-03-27 (Persist the Currents run URL outside the transient runner log)
|
||||
- Observed failure mode:
|
||||
- The watcher can include the Currents run URL in `NOTES:`, but only if it can still read the URL from live runner output or a consolidated run log.
|
||||
|
||||
Reference in New Issue
Block a user