experimental UI: be less verbose about test summaries

To keep the noise of messages in the scroll-back buffer low, limit
which test summaries are shown there.

- If a test fails to build, the error message about the build failure
  is already in the scroll-back buffer---and more useful to the user
  anyway.

- If a test is not run (either because the user interrupted the build,
  or because of a build error), then either the user is aware of it
  anyway or the information about the build failure is present and
  more useful. Also, this is only detected at the end of the build,
  were a summary of the tests is shown; hence avoid duplication here.

- If a test has status failed and there is precisely one failure log,
  then the summary does not provide any useful information compared
  to the individual FAIL message in the scrollback buffer.

While there, also show the precise status of the summary.

--
Change-Id: I13665db24f956c8d8b651dc38859649085b8bbcf
Reviewed-on: https://bazel-review.googlesource.com/#/c/3830
MOS_MIGRATED_REVID=125339810

0 files changed, 0 insertions, 0 deletions