New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 877146 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

don't run skylab_inventory changes through the CQ

Project Member Reported by akes...@chromium.org, Aug 23

Issue description

Example CL: https://chrome-internal-review.googlesource.com/c/chromeos/infra_internal/skylab_inventory/+/666051

We shouldn't need to wait on the CQ for changes like this, especially since they are often of imminent production health reasons. The CQ provides no relevant coverage (afaik).

Neither does the pre-CQ provide relevant coverage (afaik, unless there is an inventory sanity check test in some pre-cq config). So we shouldn't be using the pre-cq default set.

Is there a pre-cq config that provides any sanity verification of this repo, that we should use for pre-cq coverage here and submit-from-precq behavior?
 

Sign in to add a comment