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

Refine explicit-VM blacklist handling for ATVM runs

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 12:30:31 -04:00
parent 95eeba60cd
commit 3b28f877ef
3 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -266,3 +266,11 @@ This file stores run-specific examples only when a run produced a new learning r
- Action for future runs:
- Treat `approve` as approval to run and start the watcher.
- Treat `approve without watcher` as approval to run without starting the watcher.
## Run Learning: 2026-03-27 (Do not auto-add blacklist excludes for explicitly specified VMs)
- Observed requirement:
- When the operator explicitly specifies the VM or VM list to run, they do not want the maintained `--exclude_partial_match` blacklist added automatically.
- Action for future runs:
- Keep the maintained `--exclude_partial_match` list for broad selectors such as `--containsVm` or `--randomize`.
- When the operator uses `--specify_vms`, do not auto-add the blacklist unless they explicitly request it.
- Even when the operator uses `--specify_vms`, first check whether any requested VM is on the maintained blacklist and stop instead of launching it if one is included.