Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .bazelrc
Original file line number Diff line number Diff line change
Expand Up @@ -149,3 +149,8 @@ build:rbe_release --remote_download_toplevel

# RBE
import %workspace%/.bazelrc.remote

build --action_env=INVALIDATE_ALL_REMOTE_CACHE_ENTRIES=yes-absolutely-1
build --test_env=INVALIDATE_ALL_REMOTE_CACHE_ENTRIES=yes-absolutely-1
build --copt=-DINVALIDATE_ALL_REMOTE_CACHE_ENTRIES="yes-absolutely-1"
build --host_copt=-DINVALIDATE_ALL_REMOTE_CACHE_ENTRIES="yes-absolutely-1"
Comment on lines +153 to +156

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Unscoped bazel cache busting 🐞 Bug ➹ Performance

The added unconditional .bazelrc options change action environment and compilation flags for all
Bazel builds, which will broadly invalidate existing cache hits and increase build/test latency.
This also impacts RBE runs that rely on the configured remote cache, increasing remote
execution/cache load.
Agent Prompt
### Issue description
`.bazelrc` now unconditionally injects an env var and compiler defines into the build, which changes Bazel action keys and causes widespread cache misses (local and remote). This will slow down CI and local development, and increases load on the configured remote cache.

### Issue Context
The repo uses an RBE config with `--remote_cache` in `.bazelrc.remote`. The new flags are added as plain `build ...` options (not under a dedicated config), so they apply broadly.

### Fix Focus Areas
- .bazelrc[153-156]

### Suggested fix
- Remove these lines entirely, **or**
- Move them under an opt-in config (e.g. `build:cache_bust ...`) or a CI-only config (e.g. `build:rbe-ci ...`) so normal builds keep benefiting from caches.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Loading