From a4cc983b1e0a36d9299f26d7f3158d6e1a92e9ac Mon Sep 17 00:00:00 2001 From: Alex Eagle Date: Wed, 1 Nov 2023 16:15:13 -0700 Subject: [PATCH] Update iteration-speed.md Mention the new flag from https://github.com/bazelbuild/bazel/pull/16805 that can help prevent analysis cache discards Closes #19989. PiperOrigin-RevId: 578673354 Change-Id: I062274f8059bbfeef5fb49b9c6c26db9887efde9 --- site/en/advanced/performance/iteration-speed.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/site/en/advanced/performance/iteration-speed.md b/site/en/advanced/performance/iteration-speed.md index 1b4fcc7aba5f3d..c9b5e6698bb105 100644 --- a/site/en/advanced/performance/iteration-speed.md +++ b/site/en/advanced/performance/iteration-speed.md @@ -90,3 +90,6 @@ server was restarted. Either of these should be avoided during iterative use: * If you want to use multiple sets of flags from the same workspace, you can use multiple, distinct output bases, switched with the `--output_base` flag. Each output base gets its own Bazel server. + +To make this condition an error rather than a warning, you can use the +`--noallow_analysis_cache_discard` flag (introduced in Bazel 6.4.0)