Description of the bug:

--incompatible_remote_build_event_upload_respect_no_cache doesn't prevent the upload of no-cache/no-remote blobs if you use --remote_download_minimal or --remote_download_toplevel.

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

bazelrc:

build --bes_results_url=https://app.buildbuddy.io/invocation/
build --bes_backend=grpcs://remote.buildbuddy.io
build --remote_cache=grpcs://remote.buildbuddy.io
build --modify_execution_info=.*=+no-remote
build --incompatible_remote_build_event_upload_respect_no_cache

The above will only upload the timing profile, as expected.

Adding --remote_download_minimal or --remote_download_toplevel will cause other blobs to be uploaded.

Which operating system are you running Bazel on?

macOS

What is the output of bazel info release?

5.0.0 through last-green

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 master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

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

No response