[bazel] Allow SupportTests to be built remotely and cached #121375
Merged
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.
SupportTests
fails in the bazel macOS sandbox, becauseFileSystemTest.permissions
expects to be able to modify filepermissions on some otherwise protected files.
Previously this test was marked
local
in bazel, which hasadditional undesirable effects such as skipping remote build and cache.
Tighten the bazel tags to just
no-sandbox
. Note in particular, thatthis allows the test to build, execute, and cache remotely (if
configured).
Testing:
passes with
no-sandbox
.setup) with
no-sandbox
.