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

Issue 591211 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
█ wonderfly@chromium.org
akes...@chromium.org
█ sosa@chromium.org
vapier@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Pre-CQ should rerun if the results are stale at the time of CQ

Project Member Reported by ameyd@google.com, Mar 1 2016 
We recently had an odd build breakage because the culprit CL[1] had gone through pre-cq before another CL[2] added a new test.

Is there a mechanism to prevent such things from happening today? If not, could the CQ runner refuse to process a CL if the pre-cq results were stale (e.g., >24 hr old)?


[1] https://chrome-internal-review.googlesource.com/#/c/249524/
[2] https://chrome-internal-review.googlesource.com/#/c/249676/

Comment 1 by akes...@chromium.org, Mar 1 2016

Cc: vapier@chromium.org
https://groups.google.com/a/google.com/forum/#!topic/chromeos-infra-discuss/T2EjZhqcHw8

Are you simply asking for a shorter timeout that 7 days?

A few days might make sense. I think 24 hours is cutting it too short. We don't want to end up in a pre-cq-retry storm.

Comment 2 by ameyd@google.com, Mar 1 2016

Status: WontFix (was: Untriaged)
I had missed the discussion on chromeos-infra-discuss@.  Sorry for noise.  Closing this now.
►

Sign in to add a comment