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

atvm: default windows runs to hang_retries 0

Browse Source
This commit is contained in:
anthony.wen
2026-05-07 11:13:42 -04:00
parent 28cd8a217f
commit e3497111dd
3 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
atvm/AGENTS.md
View File

@@ -53,6 +53,7 @@ This file defines how to operate and maintain the ATVM workspace in `/home/aw/co
- Always include `--ignore_force_shutdown` unless explicitly told not to. - Always include `--ignore_force_shutdown` unless explicitly told not to.
- Always include `--test_partition` unless explicitly told not to. - Always include `--test_partition` unless explicitly told not to.
- For `cmc-migrateops-compute-migration` to VMware, default to `--vm_platforms vmware` and `--set_static_ip_dest` unless explicitly told otherwise. - For `cmc-migrateops-compute-migration` to VMware, default to `--vm_platforms vmware` and `--set_static_ip_dest` unless explicitly told otherwise.
- For ATVM automation runs that involve Windows guests, default the runner command to `--hang_retries 0` unless explicitly told otherwise.
- Default config family: `gold` - Default config family: `gold`
- Treat `cmc-systemOS` as not using plugin or integration-type arguments. Do not auto-add `--use_specified_plugin`, `--integration_type`, or watcher integration/plugin metadata for that template. - Treat `cmc-systemOS` as not using plugin or integration-type arguments. Do not auto-add `--use_specified_plugin`, `--integration_type`, or watcher integration/plugin metadata for that template.
- Do not auto-add the maintained `--exclude_partial_match` blacklist when the operator explicitly targets named VMs with `--specify_vms`. - Do not auto-add the maintained `--exclude_partial_match` blacklist when the operator explicitly targets named VMs with `--specify_vms`.

1
atvm/docs/automation/guide.md
View File

@@ -36,6 +36,7 @@ Run ATVM CMC automation tests on the designated automation VM without unintended
- Do not add plugin or integration-type arguments to `cmc-systemOS`; that template should be planned without `--use_specified_plugin`, without `--integration_type`, and without watcher integration/plugin metadata. - Do not add plugin or integration-type arguments to `cmc-systemOS`; that template should be planned without `--use_specified_plugin`, without `--integration_type`, and without watcher integration/plugin metadata.
- For `cmc-migrateops-compute-migration`, default to `--set_static_ip_dest` unless the operator explicitly says otherwise. - For `cmc-migrateops-compute-migration`, default to `--set_static_ip_dest` unless the operator explicitly says otherwise.
- For `cmc-migrateops-compute-migration` to VMware, default to `--vm_platforms vmware` unless the operator explicitly says otherwise. - For `cmc-migrateops-compute-migration` to VMware, default to `--vm_platforms vmware` unless the operator explicitly says otherwise.
- For ATVM automation runs that involve Windows guests, default `run-sorry-cypress.py` to `--hang_retries 0` unless the operator explicitly says otherwise.
- For `cmc-reboot`, treat `--use_specified_plugin both` as an exception case that requires an extra confirmation. - For `cmc-reboot`, treat `--use_specified_plugin both` as an exception case that requires an extra confirmation.
- When `cmc-reboot` is planned with `--use_specified_plugin both`, warn that FC+iSCSI together may hit a "chicken before the egg" timing problem where iSCSI disks are not attached before mTDI / CMC services start. - When `cmc-reboot` is planned with `--use_specified_plugin both`, warn that FC+iSCSI together may hit a "chicken before the egg" timing problem where iSCSI disks are not attached before mTDI / CMC services start.
- For `cmc-reboot`, prefer `--use_specified_plugin fc` or `--use_specified_plugin iscsi` unless the operator explicitly reconfirms that `both` is really intended after seeing that warning. - For `cmc-reboot`, prefer `--use_specified_plugin fc` or `--use_specified_plugin iscsi` unless the operator explicitly reconfirms that `both` is really intended after seeing that warning.

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

@@ -26,6 +26,13 @@ This file stores run-specific examples only when a run produced a new learning r
- For `cmc-migrateops-compute-migration`, include `--set_static_ip_dest` by default unless the operator explicitly asks not to. - For `cmc-migrateops-compute-migration`, include `--set_static_ip_dest` by default unless the operator explicitly asks not to.
- Keep platform selection (`--vm_platforms ...`) based on the operator request while retaining this static-IP default. - Keep platform selection (`--vm_platforms ...`) based on the operator request while retaining this static-IP default.
## Run Learning: 2026-05-07 (Default Windows-involved ATVM runs to hang retries 0)
- Observed requirement:
- When an ATVM automation run involves Windows guests, runner retry loops should be disabled by default to avoid long post-failure wait cycles.
- Action for future runs:
- For Windows-involved ATVM automation runs, add `--hang_retries 0` to `run-sorry-cypress.py` by default unless the operator explicitly requests a different value.
- Keep this as an operator-default behavior even though the underlying runner option is generic and not Windows-only in code.
## Run Learning: 2026-05-02 (Do not reuse the previous controller status check for a new ATVM request) ## Run Learning: 2026-05-02 (Do not reuse the previous controller status check for a new ATVM request)
- Observed failure mode: - Observed failure mode:
- A later ATVM run request was blocked because the assistant reused the immediately previous controller status result instead of performing a fresh live running-state check at request time. - A later ATVM run request was blocked because the assistant reused the immediately previous controller status result instead of performing a fresh live running-state check at request time.