Description of the feature request:

Current behavior is for bazel to display an error message in output, and proceed running entire build without remote cache. This leads to user experiencing huge build time, without knowing everything is being rebuilt on your machine. We'd like an option to fail the build immediately and force user to retry.

We also suspect cases where user briefly loosing internet connectivity in the middle of a bazel build, which disabled remote cache for the rest of the build.

Which category does this issue belong to?

No response

What underlying problem are you trying to solve with this feature?

No response

Which operating system are you running Bazel on?

No response

What is the output of bazel info release?

No response

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 ?

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response