Add ATVM systemd runner service
This commit is contained in:
@@ -78,6 +78,7 @@ This file defines how to operate and maintain the ATVM workspace in `/home/aw/co
|
||||
- Unless the operator explicitly reconfirms `both` for `cmc-reboot`, prefer only `fc` or only `iscsi`, not both.
|
||||
- When the watcher is requested, start the watcher before `run-sorry-cypress.py`.
|
||||
- When the watcher is requested, build the watcher-start command so it automatically includes the exact approved `cmc-templates.py` command via `--template-command` and the exact approved `run-sorry-cypress.py` command via `--runner-command`; the operator should not need to restate them separately.
|
||||
- When watcher-backed execution is used, prefer the controller-local `atvm-runner@...` systemd service over detached SSH background launch patterns for `run-sorry-cypress.py`.
|
||||
- Do not start the runner before the watcher, because the watcher helper clears stale `/tmp/<build-name>.log` and can delete the fresh live runner log if the runner starts first.
|
||||
- For host-level test detail and failed-test investigation, use `/root/cdc-e2e-cyp-12.17.4/cypress/cmcReporter`, especially `logs/`, `xml/`, and `mochawesome/`.
|
||||
- Apply failed-host detail recovery consistently for every ATVM template run, not just `cmc-reboot`.
|
||||
|
||||
Reference in New Issue
Block a user