New issue
Advanced search Search tips

Issue 898977 link

Starred by 1 user
Status: Duplicate
Merged: issue 840933
Owner: ----
Closed: Oct 25
Cc:
jclinton@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

PreCQ launcher did not notify Gerrit of failure for ~18 hours

Project Member Reported by dhanyaganesh@google.com, Oct 25 
See here:
https://chromium-review.googlesource.com/c/chromiumos/chromite/+/1266017

The change caused VMTests in betty-pre-cq and betty-arcnext-pre-cq to wait forever. The individual jobs have failed status. But the launcher itself has not returned that result to Gerrit.

Comment 1 by dgarr...@chromium.org, Oct 25

Mergedinto: 840933
Status: Duplicate (was: Untriaged)
That build ran until it hit the 4 hour timeout for PreCQ jobs, and was then killed. The way it was killed meant CIDB was never updated, and the PreCQ Launcher uses CIDB, not buildbucket (which had valid data).

This is a specific instance of crbug.com/840933
►

Sign in to add a comment