Remote gRPC cache failure fails the build #27734
Description
Description of the bug:
I'd like to fall back to a local build rather than failing the build entirely when the cache is unavailable, like when the VPN is down or it's having other troubles, but I can't seem to make it happen.
This feels like a duplicate issue because I've found several similar past issues. #25965 in particular describes the behavior I want but can't seem to actually achieve.
My builds immediately fail with the error:
ERROR: /home/josh/.cache/bazel/_bazel_josh/0366260ff7e5bd26191001b262965e9c/external/rules_go++go_sdk+main___host_0/BUILD.bazel:77:15: GoToolchainBinaryBuild external/rules_go++go_sdk+main___host_0/builder [for tool] failed: Failed to query remote execution capabilities: UNAVAILABLE: Unable to resolve host my.internal.buildbuddy.url
Am I missing something? Has behavior been changed since the other issues I linked that indicate that it should be falling back to a local build? Is this a regression?
It seems like it changed in version 8.0.0. Version 7.7.1 will continue the build locally if the remote cache fails, but starting at 8, the build fails if the cache fails.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
Ubuntu 24.04
What is the output of bazel info release?
release 8.4.2
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse HEAD ?
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
Any other information, logs, or outputs that you want to share?
My bazelrc contents:
build --remote_retries=0
build --remote_local_fallback=1
build --remote_cache=grpcs://my.internal.buildbuddy.url