Bazel cache misses across machines
The machines are computing different action keys or cannot retrieve the same cached entries. A shared endpoint alone does not guarantee shareable actions.
Common causes
- Different command-line flags or layered bazelrc files
- Environment variables or host paths leak into actions
- Toolchain or execution-platform differences
- Authentication, namespace, instance-name, or read-policy differences
What to check
- Capture comparable execution logs for the same commit and target
- Compare command lines, environment, inputs, tool paths, and platform properties
- Verify remote instance name and read/write settings
- Confirm both machines can retrieve a known digest
Primary sources
Use these references to confirm protocol and version-specific behavior.
Investigate with build-level evidence
Hermetiq correlates Bazel actions, cache behavior, Buildbarn infrastructure, and remote-execution timing so teams can move from a status code to the build and system behavior behind it.
Technical review: July 20, 2026 · Verify flags and behavior against the Bazel and Buildbarn versions deployed in your environment.