[dev qa] limit remote cache usage#11333
Merged
dan-stowell merged 4 commits intomasterfrom Feb 18, 2026
Merged
Conversation
Co-authored-by: Shelley <shelley@exe.dev>
Co-authored-by: Shelley <shelley@exe.dev>
The previous approach of --noremote_accept_cached + --remote_cache= was insufficient because: 1. --remote_cache= (empty) is a no-op when --remote_executor is set; the executor endpoint always provides AC and CAS. 2. --noremote_accept_cached only sets skip_cache_lookup=true in the Execute RPC, but --remote_download_minimal causes Bazel to make separate GetActionResult calls for output resolution, which bypass skip_cache_lookup and hit the AC directly. The fix uses --remote_instance_name=dev-qa-test/<unique-id> to place each run in a fresh cache namespace. This guarantees zero AC hits since no previous results exist in that namespace. Combined with the existing --noremote_accept_cached (belt-and-suspenders for the Execute RPC path), this ensures all actions are freshly executed. Also removes the no-op --remote_cache= flag. Co-authored-by: Shelley <shelley@exe.dev>
…ote-cache --remote_download_minimal is fundamentally incompatible with 'no cache': it relies on the AC to track remote outputs, causing GetActionResult RPCs that produce AC hits even with --noremote_accept_cached (which only affects the Execute RPC's skip_cache_lookup field). Replace it with --modify_execution_info=.*=+no-remote-cache which tags all actions with 'no-remote-cache', preventing both AC reads AND writes while still allowing CAS (required for remote execution). Co-authored-by: Shelley <shelley@exe.dev>
Contributor
|
Can we have dev QA do both of these things?
edit: it would also be really nice to test the second item above through the cache proxy (grpcs://proxy.metal.buildbuddy.dev). |
tempoz
approved these changes
Feb 18, 2026
Contributor
tempoz
left a comment
tempoz
left a comment
There was a problem hiding this comment.
This looks good to me; to Tyler French's comment I would say that that sounds like a useful test, but I think that this was unintended behavior and this should be viewed as a bugfix, whereas that could be its own PR adding an additional test.
tyler-french
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I would like the Dev QA tests to actually exercise RBE regardless of the state of the remote cache (yay hermiticity!).
This change uses a fresh run ID per test run, and adds flags to reduce AC usage.
The
buildbuddyDev QA test really explodes (20K+ executions), while others see very few executions.Choosing different targets or repos can exercise RBE more fully.