New issue
Advanced search Search tips

Issue 866717 link

Starred by 2 users
Status: Duplicate
Merged: issue 819307
Owner: ----
Closed: Aug 10
Cc:
la...@chromium.org
jclinton@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

CQ shouldn't slam my CLs twice for the same failure to start a trybot

Project Member Reported by diand...@chromium.org, Jul 23 
See <https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1147118>

Summary of events:

11:10: marked trybot ready
15:29: trybot timed out after 240 minutes
15:34: marked trybot ready again
15:37: trybot timed out after 240 minutes


...so the second slamming of my CL either was due to the first timeout hitting twice or the CL is counting really really fast.

Comment 1 by diand...@chromium.org, Jul 23

Cc: la...@chromium.org
CC current infra on-call to triage.

Comment 2 by jclinton@chromium.org, Jul 24 

What is "slamming"? What's the actual problem?

Comment 3 by diand...@chromium.org, Jul 24

Cc: jclinton@chromium.org
Slam = marked my CL as not ready.

...the CQ marked my CL as not ready twice.  Once at 15:29 and once at 15:37.  Said another way: I went through and manually marked my CL as ready again at 15:34 and then got frustrated because the CQ unmarked it at 15:37.

Comment 4 by saklein@chromium.org, Aug 9 

I have also run into this issue. See: https://chromium-review.googlesource.com/c/chromiumos/overlays/eclass-overlay/+/1165943

2018-08-08 17:21: Failed and set to TR=0.
2018-08-09 09:08: I set it back to TR=1.
2018-08-09 09:09: Messages about 1) it being picked up by pre-cq, 2) it timed out after 240 minutes, and 3) was set to TR=0.

Comment 5 by jclinton@chromium.org, Aug 10

Mergedinto: 819307
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment