build: increase Bazel shard counts for slow integration test targets - #34229
Merged
Merged
Conversation
Increase Bazel test shard counts for slow integration test targets to improve CI execution times: - //packages/angular/build:unit-test_integration_tests: 5 -> 10 - //packages/angular/build:library_integration_tests: 4 -> 6 - //packages/angular_devkit/build_angular:build_angular_dev-server_test: 10 -> 12 - //packages/angular_devkit/build_angular:build_angular_karma_test: 6 -> 10 - //packages/angular_devkit/build_angular:build_angular_server_test: 2 -> 6 - //packages/angular_devkit/build_angular:build_angular_browser_test: 10 -> 20 - //packages/angular_devkit/build_angular:build_angular_prerender_test: 2 -> 4
angular-robot
Bot
added
the
area: build & ci
alan-agius4
added
action: review
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request increases and adds shard counts for several integration tests and large specs in the Bazel build configuration files, specifically within packages/angular/build/BUILD.bazel and packages/angular_devkit/build_angular/BUILD.bazel. These adjustments, which include increasing shards for unit-test_integration_tests, library_integration_tests, dev-server, karma, and browser, as well as introducing shards for server and prerender, aim to improve test parallelization and execution speed. There are no review comments, and I have no feedback to provide.
alan-agius4
requested review from
josephperrott
and removed request for
clydin
October 1, 2026 15:30
alan-agius4
added
action: merge
Collaborator
Author
|
This PR was merged into the repository. The changes were merged into the following branches:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Increase Bazel test shard counts for slow integration test targets to improve CI execution times:
//packages/angular/build:unit-test_integration_tests: 5 -> 10//packages/angular/build:library_integration_tests: 4 -> 6//packages/angular_devkit/build_angular:build_angular_dev-server_test: 10 -> 12//packages/angular_devkit/build_angular:build_angular_karma_test: 6 -> 10//packages/angular_devkit/build_angular:build_angular_server_test: 2 -> 6//packages/angular_devkit/build_angular:build_angular_browser_test: 10 -> 20//packages/angular_devkit/build_angular:build_angular_prerender_test: 2 -> 4