Fix windows 2019 staleness issue #17225
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.
Bazel on windows doesn't sandbox very well, and our old strategy for bootstrap staleness test was causing some non-deterministic failures. Before, we were creating multiple genrules copying the same batch of files, but only marking a specific one as the output of each. That works fine with proper sandboxing, but on windows can cause conflicts. With this change, each genrule limits its scope to only copy the 1 file it's meant to generate