Tiago Quelhas

The intention behind `--remote_local_fallback` was indeed for it to only apply to remote execution. So this should be considered a feature request to add a similar feature for remote caching....

There are two distinct issues here. 1. The fact that `--remote_local_fallback` doesn't cause a fallback to occur for local execution with a remote cache is a FR (because the flag...

I have a hunch: does setting `--noexperimental_inmemory_dotd_files` make the issue go away? Otherwise, capturing a `--experimental_remote_grpc_log` (log of all of the interactions between Bazel and the remote cache) should make...

Thanks for confirming my suspicion; that gives me a hint as to where the problem might be. Do you mind filing a fresh issue so we can track it separately?

"Building without the bytes" as currently implemented only applies to output artifacts (as opposed to source artifacts). If I understand it correctly, you're asking to extend it to cover source...

Does this repro with `--noexperimental_merged_skyframe_analysis_execution`? I'm wondering if it's the limitation described in this commit description (and afaik not yet lifted since then): https://github.com/bazelbuild/bazel/commit/d94816a68980628e43f509bcd6a49e98984658b5 (although I would concur that `bazel...

Please reopen with repro instructions.

We looked for something that could go wrong with the combination of `--remote_cache`, `--remote_download_all` and `--experimental_inmemory_dotd_files`, but don't have a plausible theory yet (other than the remote cache spuriously evicting...

@luispadron Can you provide the `--experimental_remote_grpc_log` for a build exhibiting this failure? Otherwise, it's going to be difficult to make progress on this.

@miscott2 I think the `--experimental_remote_grpc_log` for one of the failed runs would be the most useful piece of information here. (You can scrub any sensitive information, but please preserve the...