Assigning to dgarrett@ on the theory that, if the problem is
easy to understand, he's the most likely to see it.

In the linked build, coral-paladin is important=false

It is also failing, AND marked experimental in build status.

https://uberchromegw.corp.google.com/i/chromeos/builders/coral-paladin

If it's expected to be green, but dealing with a temporary failure, it should be important in the config, and experimental in the build status.

If it's still a new untrusted builder, the current config is correct, but the build status should be cleared, and there should be someone owning the process of making it green.

I think Charles might know what the team is doing there. I'm not sure.

+YH whom may know about investigations into Coral hwtest stability.

There have been ongoing infrastructure stability issues.  The most recent one was the alloc for astronaut was taken away for some reason, but that has since been resolved. 

It appears to be another issue now.

Either way, I've yet to see something that wasn't infrastructure related to these flakes yet.

So.... you are saying we should mark the build as important in both the build config, and the build status?

it was unmarked base on crbug.com/788584

I would defer to that as the main root of determining whether to mark as important or not

I just started to make that change, and found that it's marked as experimental because of https://crbug.com/788584. Is that still relevant?

It's not clear to me whether bug 788584 is still a thing or
not.  However, I think our best way forward is this:
 1) Commit the change to make the builder important again.
 2) Leave the builder EXPERIMENTAL in the tree status.
 3) Work to resolve the problems and make the builder green.

Regarding item 3), we'll probably need to file new bugs for whatever
problems there are, and we'll need engagement from sheriffs and/or
coral experts to debug the problems.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/0e1d4133f9c0ef5a5cffb04591ee6d939a66b074

commit 0e1d4133f9c0ef5a5cffb04591ee6d939a66b074
Author: Don Garrett <dgarrett@google.com>
Date: Sat Jan 06 05:14:14 2018

chromeos_config: Mark coral-paladin important.

BUG= chromium:799196 ,chromium:788584
TEST=chromeos_config_unittest

Change-Id: I747a4310f7753459f42ed47270dd06fa97be74e5
Reviewed-on: https://chromium-review.googlesource.com/853114
Commit-Ready: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@google.com>
Reviewed-by: C Shapiro <shapiroc@google.com>

[modify] https://crrev.com/0e1d4133f9c0ef5a5cffb04591ee6d939a66b074/cbuildbot/config_dump.json
[modify] https://crrev.com/0e1d4133f9c0ef5a5cffb04591ee6d939a66b074/cbuildbot/chromeos_config.py

I'm calling this fixed, since the builder is now important.

Regarding making the paladin green, there's  bug 799997 ; I'm
reliably informed that that's our only known obstacle.