New issue
Advanced search Search tips

Issue 887094 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Ensure VMTests are Opt-In per build config, not opt out.

Project Member Reported by dgarr...@chromium.org, Sep 19

Issue description

We 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.
 
Cc: yshaul@chromium.org
Owner: yshaul@chromium.org
Status: Assigned (was: Untriaged)
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.
Status: WontFix (was: Assigned)
This will be the default in parallel cq

Sign in to add a comment