Switch bazel default spawn strategy to sandboxed
#9168
Merged
Conversation
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
qihqi
approved these changes
May 15, 2025
zhanyong-wan
added a commit
that referenced
this pull request
May 20, 2025
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.
For #9061.
Two reasons for this change:
sandboxedis a better practice thanstandaloneas it enforces explicit build dependency declaration.standalonemode leads to an error. Clang works with thesandboxedmode.If you use the dev container for developing PyTorch/XLA and you previously cloned the repo without world-readability, you may run into permission issues building PyTorch/XLA after this commit. To fix that, go to the workspace directory and run
chmod -R o+rX .. This is also documented in.bazelrc.basediff: #9156