a non-important builder should never cause the CQ to fail |
||
Issue descriptionSee issue 613868. In this case the builder for amd64-generic failed to start because the hardware was borked.
,
May 24 2016
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.
,
May 24 2016
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.
,
May 24 2016
OK, let's close it then. Please reopen if you have additional info/opinions. |
||
►
Sign in to add a comment |
||
Comment 1 by akes...@chromium.org
, May 24 2016