Ensure VMTests are Opt-In per build config, not opt out. |
||||
Issue descriptionWe don't normally want to run VMTests other than on a very limited subset of builders and boards (betty and amd64-generic). This should be reflected in the way that chromeos_config is organized by making them "opt-in" on a per build config basis, not opt out like they currently are. One specific example is that "no-vmtest-pre-cq" build configs should be able to go away, since they are no longer a meaningful distinction.
,
Oct 25
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
,
Jan 15
This will be the default in parallel cq |
||||
►
Sign in to add a comment |
||||
Comment 1 by dgarr...@chromium.org
, Oct 24