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

Issue 614214 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

a non-important builder should never cause the CQ to fail

Project Member Reported by semenzato@chromium.org, May 23 2016

Issue description

See issue 613868.  In this case the builder for amd64-generic failed to start because the hardware was borked.
 
What do you mean by non-important? As far as chromite is concerned, this config is important=True.
OK.  I admit don't really know how "important" this builder is.  It could be that if it fails because the hardware is down, it probably shouldn't stop the CQ.

Then again, how often does this happen?

Let's collect a few more opinions.  I am OK with closing this as Won't Fix.
When I looked it up early this morning, I found it wasn't important. Did I make a mistake with the look up?

Oh... I guess I did. Silly me. Yeah, that would be the issue.
Status: WontFix (was: Untriaged)
OK, let's close it then.  Please reopen if you have additional info/opinions.

Sign in to add a comment