New issue
Advanced search Search tips

Issue 707899 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature

Blocked on:
issue 707897



Sign in to add a comment

Update CIDB state after pre-startup failure (discovered via buildbucket).

Project Member Reported by dgarr...@chromium.org, Apr 3 2017

Issue description

There are some cases where slaves fail before getting far enough to ever update CIDB at all.

These cases can be detected via buildbucket.

Examples include:
1) Builders that are offline.
2) Builders that have no CIDB credentials.
3) Builds that fail in the build recipe or very early in cbuidlbot.

It could be nice to notice these cases and update CIDB to reflect what happened based on the buildbucket data. It might be appropriate do this this in a CIDB cleanup script such as has been proposed in crbug.com/707897.
 
Owner: dgarr...@chromium.org

Comment 2 by aut...@google.com, Apr 4 2017

Labels: -current-issue
Status: Available (was: Untriaged)
Labels: -Type-Bug Type-Feature
Owner: ----
Components: Infra>Client>ChromeOS>CI
Components: -Infra>Client>ChromeOS

Comment 7 by nxia@chromium.org, Jun 8 2018

Cc: -nxia@chromium.org

Sign in to add a comment