From 2e7a5b47979b2679208a97a65df265be953eb595 Mon Sep 17 00:00:00 2001 From: Googler Date: Tue, 21 Jul 2015 15:27:35 +0000 Subject: Fixed bug where blaze run with the --color=no flag was still printing out in color when the build fails. -- MOS_MIGRATED_REVID=98736813 --- .../com/google/devtools/build/lib/runtime/commands/InfoCommand.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/main/java/com/google/devtools/build/lib/runtime/commands/InfoCommand.java') diff --git a/src/main/java/com/google/devtools/build/lib/runtime/commands/InfoCommand.java b/src/main/java/com/google/devtools/build/lib/runtime/commands/InfoCommand.java index 2448d90aca..d1f18cefcd 100644 --- a/src/main/java/com/google/devtools/build/lib/runtime/commands/InfoCommand.java +++ b/src/main/java/com/google/devtools/build/lib/runtime/commands/InfoCommand.java @@ -181,8 +181,8 @@ public class InfoCommand implements BlazeCommand { @Override public ExitCode exec(final BlazeRuntime runtime, final OptionsProvider optionsProvider) { + runtime.getReporter().switchToAnsiAllowingHandler(); Options infoOptions = optionsProvider.getOptions(Options.class); - OutErr outErr = runtime.getReporter().getOutErr(); // Creating a BuildConfiguration is expensive and often unnecessary. Delay the creation until // it is needed. -- cgit v1.2.3