experimental UI: present SUBCOMMANDS in the scroll-back buffer

Treat SUBCOMMAND events the same way as ERROR/WARNING/INFO commands in the
experimental UI: they provide information the user wants to look up later.
As SUBCOMMAND events are only raised if that information is requested by the
user, providing this information does run the risk over overwhelming the user
with information.

--
Change-Id: Ia7adeb2d5b92f18b8b88b026f790ac2af47b59d4
Reviewed-on: https://bazel-review.googlesource.com/#/c/3201
MOS_MIGRATED_REVID=118678085

1 files changed, 3 insertions, 0 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/runtime/ExperimentalEventHandler.java b/src/main/java/com/google/devtools/build/lib/runtime/ExperimentalEventHandler.java
index 1185ae4327..a67dc2abfd 100644
--- a/src/main/java/com/google/devtools/build/lib/runtime/ExperimentalEventHandler.java
+++ b/src/main/java/com/google/devtools/build/lib/runtime/ExperimentalEventHandler.java
@@ -94,6 +94,7 @@ public class ExperimentalEventHandler extends BlazeCommandEventHandler {
           case ERROR:
           case WARNING:
           case INFO:
+          case SUBCOMMAND:
             if (!buildComplete) {
               clearProgressBar();
             }
@@ -131,6 +132,8 @@ public class ExperimentalEventHandler extends BlazeCommandEventHandler {
       case INFO:
         terminal.textGreen();
         break;
+      case SUBCOMMAND:
+        terminal.textBlue();
     }
   }