If a remote cache returns a failed action (exit code != 0) then Bazel should treat this as a cache miss and attempt to re-execute the action. See for details https://gitlab.com/BuildGrid/buildgrid/issues/151
We need to fix this for remote execution and caching across all protocols. In the case of remote execution, we'll also need to set skip_cache_lookup to true in order to ensure re-execution.
Most helpful comment
We need to fix this for remote execution and caching across all protocols. In the case of remote execution, we'll also need to set
skip_cache_lookuptotruein order to ensure re-execution.