Description of the problem / feature request:
When using --incompatible_remote_results_ignore_disk + --disk_cache, --incompatible_remote_build_event_upload_respect_no_cache no longer prevents uploads to BES.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
This will exclude blobs from upload:
$ git clone [email protected]:bazelbuild/rules_apple.git
$ cd rules_apple
$ env USE_BAZEL_VERSION=3ea70282c5795670070d8cb546cac8aa321d79ce bazelisk build --remote_cache=grpcs://remote.buildbuddy.io --bes_backend=grpcs://remote.buildbuddy.io --bes_results_url=https://app.buildbuddy.io/invocation/ --incompatible_remote_build_event_upload_respect_no_cache --noremote_upload_local_results --disk_cache=/tmp/bazel_disk_cache //examples/iOS/StickersApp
While this won't:
$ env USE_BAZEL_VERSION=3ea70282c5795670070d8cb546cac8aa321d79ce bazelisk build --remote_cache=grpcs://remote.buildbuddy.io --bes_backend=grpcs://remote.buildbuddy.io --bes_results_url=https://app.buildbuddy.io/invocation/ --incompatible_remote_build_event_upload_respect_no_cache --noremote_upload_local_results --disk_cache=/tmp/bazel_disk_cache --incompatible_remote_results_ignore_disk //examples/iOS/StickersApp
What operating system are you running Bazel on?
macOS 12.0.1
What's the output of bazel info release?
Bazel built from HEAD to have #14451 in it.
Have you found anything relevant by searching the web?
#14338