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

Issue 673465 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Pre-CQ not registering success, not accepting newly-verified commits from trybot.

Project Member Reported by jeffandersen@google.com, Dec 12 2016

Issue description

Each pre-cq build has succeeded for my commit, but I have received no notification to that effect. In addition, though this commit should be submitted on pre-cq success, it has not occurred yet.

akeshet@ believes it may be due to the pre-cq-launcher crashing somewhere before it finishes each tick.

Affected commit: https://chrome-internal-review.googlesource.com/#/c/311017/

Pre-CQ status: https://viceroy.corp.google.com/chromeos/pre-cq
 

Comment 1 by nxia@chromium.org, Dec 12 2016

Status: Started (was: Untriaged)
I'll take a look
Note that various pre-cq related CL actions also took a nosedive around the same time as the pre-cq status metric outage. https://viceroy.corp.google.com/chromeos/cl-actions
Maybe the pre-cq-launcher somehow lost it's cidb connection and ability to connect to cidb? Behavior seems sort of consistent with that.
Suggestion: abort pre-cq launcher. See if it makes it past BuildStart stage and that it has a valid build id in cidb  (and entry there)

Comment 5 by nxia@chromium.org, Dec 12 2016

Pre-cq-launcher #8250 hung there since 10:39:46. suspecting that to be a GOB outage like  crbug.com/661704 .
Restarted pre-cq-launcher. Will see if it works.  
Status: Fixed (was: Started)
pre-cq-launcher is working now, per metrics.

Sign in to add a comment