Remove 50-shard limit on test shard_count - #20
Draft
dmiller-figma wants to merge 6455 commits into
Draft
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
19 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.
Description
Base the Figma fork on upstream Bazel 9.2.0 and carry forward the existing shard-count compatibility change. Some fork consumers intentionally use more than 50 test shards.
Changes
Test Plan
USE_BAZEL_VERSION=9.2.0 bazel test //src/test/java/com/google/devtools/build/lib/analysis:RuleConfiguredTargetTest