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

Issue 831467 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ dianwa@chromium.org
akes...@chromium.org
█ jkop@chromium.org
█ pbe...@chromium.org
sheckylin@chromium.org
hidehiko@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature



Sign in to add a comment

manifest changes should be tested on PreCQ and CQ

Project Member Reported by nya@chromium.org, Apr 11 2018 
CL:*604964 wrongly edited manifest-internal and make CQ red for consecutive 37 runs (!), 14 hours.
https://chrome-internal-review.googlesource.com/c/chromeos/manifest-internal/+/604964

Mistake always happens, so I won't blame the author. I rather see two big infra issues here:

1. Why didn't pre-CQ catch this issue?
2. Why wasn't this change excluded from CQ after failure?

Comment 1 by akes...@chromium.org, Apr 11 2018

Cc: pbe...@chromium.org sheckylin@chromium.org dianwa@chromium.org jkop@chromium.org

Comment 2 by jclinton@chromium.org, Apr 11 2018

Status: Assigned (was: Untriaged)

Comment 3 by pbe...@chromium.org, Apr 16 2018

Labels: Hotlist-CrOS-Sheriffing

Comment 4 by jclinton@chromium.org, Aug 7

Labels: -Type-Bug Type-Feature
Owner: ----
Status: Available (was: Assigned)
Summary: manifest changes should be tested on PreCQ and CQ (was: Investigate why we could not prevent long CQ outage)

Comment 5 by jclinton@chromium.org, Aug 7

Labels: -Pri-2 Pri-1
►

Sign in to add a comment