Update the client's skeleton logging framework to use it for --client_debug.

We are still unable to turn this on to write to files, but there are currently 2 logging systems in use in the client: the inactive one, and the print-to-stderr option triggered by --client_debug. Combine these, so we can use the same logging format for both.

Also combine it with the VerboseLogging functionality - it was not documented anywhere and seems redundant.

RELNOTES: None.
PiperOrigin-RevId: 189979051

1 files changed, 3 insertions, 1 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/runtime/BlazeServerStartupOptions.java b/src/main/java/com/google/devtools/build/lib/runtime/BlazeServerStartupOptions.java
index a033e7da19..a640e6ff42 100644
--- a/src/main/java/com/google/devtools/build/lib/runtime/BlazeServerStartupOptions.java
+++ b/src/main/java/com/google/devtools/build/lib/runtime/BlazeServerStartupOptions.java
@@ -400,7 +400,9 @@ public class BlazeServerStartupOptions extends OptionsBase {
     category = "server startup",
     documentationCategory = OptionDocumentationCategory.BAZEL_CLIENT_OPTIONS,
     effectTags = {OptionEffectTag.AFFECTS_OUTPUTS, OptionEffectTag.BAZEL_MONITORING},
-    help = "If true, log debug information from the client to stderr"
+    help =
+        "If true, log debug information from the client to stderr. Changing this option will not "
+            + "cause the server to restart."
   )
   public boolean clientDebug;