Tell remote execution to not use remote cache internally #17198
Merged
Conversation
This file contains 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
Eric-Arellano
added
the
category:internal
stuhood
reviewed
Oct 12, 2022
# Building wheels and fs_util will be skipped. Delete if not intended. [ci skip-build-wheels]
Eric-Arellano
changed the title
--no-remote-cache
# Building wheels and fs_util will be skipped. Delete if not intended. [ci skip-build-wheels]
…read-opt-impacts-proto
stuhood
approved these changes
Oct 14, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #17142.
We rely on the RemoteCache command runner for caching with remote execution. We always disable remote servers from doing caching themselves not only to avoid wasted work, but more importantly because they do not have our same caching semantics, e.g.
ProcessCacheScope.SUCCESSFULvsProcessCacheScope.ALWAYS.