Modification to remote (and disk) caches should invalidate persistent action cache remote metadata #23841
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Description of the bug:
When changing cache locations and/or cache options, the metadata stored in the persistent action cache becomes stale. Bazel starts erroring on missing remote blobs. Its easy to reproduce with remote execution and bwtb.
Just like when some flag changes invalidate the evaluation cache, I think changes to cache-related flags should invalidate the remote metadata in the persistent action cache.
This is a bit more tricky, because changes to these flags may or may not stem from a concrete change in the cache (like the cache secret key), but better safe than sorry. Invalidating that cache is not a huge loss, and cache changes are not supposed to happen frequently.
Then only way I know to discard that cache is
bazel clean, which is more aggressive than needed because it also discards local data.Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
Ubuntu
What is the output of
bazel info release?bazel 7.2
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
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
The text was updated successfully, but these errors were encountered: