x/build/dashboard, x/build/app/appengine: add ability to mark builders with a known issue

[dmitshur]

Currently, all builder failures are displayed the same way on the build.golang.org dashboard, with a red "fail" text linking to the failure log:

Due to new OS versions, new ports, or new features, there are times when a builder is just being added. It is infeasible to guarantee a builder will report useful results as soon as it is added. Trying to make that the case would cause additional overhead and stress, without a good reason.

We can add a field to the dashboard.BuildConfig struct to mark builders as having a known issue and display such builders on the build.golang.org dashboard in a way that makes it easier to see that it's not a new regression that needs to be investigated anew (by many people looking at build.golang.org).

/cc @toothrot @cagedmantis @andybons @bcmills @danscales

[dmitshur]

Here's what I've prototyped locally (note the linux-amd64-staticlockranking builder column displayed in gray):

I realize that copying the issue number out of a tooltip isn't easy. I'm open to a suggestion how to make it better with the constraint that it shouldn't take up additional space and keeping in mind it doesn't need to be done often.

[gopherbot]

Change https://golang.org/cl/227379 mentions this issue: dashboard, app/appengine: set a known issue for staticlockranking builder

[dmitshur]

A test version is deployed and can temporarily be seen at .... It looks like this:

[bcmills]

I realize that copying the issue number out of a tooltip isn't easy. I'm open to a suggestion how to make it better with the constraint that it shouldn't take up additional space and keeping in mind it doesn't need to be done often.

The builder name at the top of the column isn't currently hyperlinked. Perhaps add a hyperlink from the header to the bug?

[gopherbot]

Change https://golang.org/cl/226977 mentions this issue: dashboard, env/netbsd-{amd64,386}: add NetBSD 9.0 builders