From e6b43637ce65b3e9bcbc7e918aa5714346ae22de Mon Sep 17 00:00:00 2001 From: Tiago Quelhas Date: Tue, 13 Feb 2024 22:41:11 +0100 Subject: [PATCH] [7.1.0] Document --cache_computed_file_digests. (#21326) It seems pretty important to document the existence of this flag, as it has implications for both performance and correctness. See https://github.com/bazelbuild/bazel/issues/14401 for prior discussion. PiperOrigin-RevId: 606545000 Change-Id: I3aa9d311c805ebf9fb7401b79f320e1ba11d2179 --- .../com/google/devtools/build/lib/exec/ExecutionOptions.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/java/com/google/devtools/build/lib/exec/ExecutionOptions.java b/src/main/java/com/google/devtools/build/lib/exec/ExecutionOptions.java index 9806ac021b7c7a..2433fc08b87ee9 100644 --- a/src/main/java/com/google/devtools/build/lib/exec/ExecutionOptions.java +++ b/src/main/java/com/google/devtools/build/lib/exec/ExecutionOptions.java @@ -358,7 +358,7 @@ public boolean usingLocalTestJobs() { @Option( name = "cache_computed_file_digests", defaultValue = "50000", - documentationCategory = OptionDocumentationCategory.UNDOCUMENTED, + documentationCategory = OptionDocumentationCategory.BUILD_TIME_OPTIMIZATION, effectTags = {OptionEffectTag.UNKNOWN}, help = "If greater than 0, configures Bazel to cache file digests in memory based on their "