Currently the LUCI UI for Go builds isn't very direct, especially in the common case of a test failure.
For example:
The "FAILURE" line is redundant, the "exit status 1" line is also not very useful (more useful for an infra failure, less useful for a test failure), and the "Links" section has only one link that goes to a more verbose set of information. Nowhere here do we link to the test results directly (we do for main Go repo builds, but that also includes less useful information, like the shard number).
@rsc proposed including a summary of the test failure text instead, which I believe is the right call. We already plumb around the fact that a test failed anyway.
I'll defend the existence of the go on <x> and website on <y> lines, because I don't believe that information is surfaced very well anywhere else in the UI, but other than that, the summary markdown could use a rethink.
Currently the LUCI UI for Go builds isn't very direct, especially in the common case of a test failure.
For example:
The "FAILURE" line is redundant, the "exit status 1" line is also not very useful (more useful for an infra failure, less useful for a test failure), and the "Links" section has only one link that goes to a more verbose set of information. Nowhere here do we link to the test results directly (we do for main Go repo builds, but that also includes less useful information, like the shard number).
@rsc proposed including a summary of the test failure text instead, which I believe is the right call. We already plumb around the fact that a test failed anyway.
I'll defend the existence of the
go on <x>andwebsite on <y>lines, because I don't believe that information is surfaced very well anywhere else in the UI, but other than that, the summary markdown could use a rethink.