ci: reduce bazel test shards for browser builder test#25622
Merged
clydin merged 2 commits intoangular:mainfrom Aug 3, 2023
Merged
ci: reduce bazel test shards for browser builder test#25622clydin merged 2 commits intoangular:mainfrom
clydin merged 2 commits intoangular:mainfrom
Conversation
Reduce the number of test shards for the browser builder from 50 to 10. 50 is more than needed and can cause excessive resource usage.
eb0e2f2 to
93bc6be
Compare
In the TS standard decorator E2E test a JIT production build is executed. The bundle budgets are now removed from this test step to prevent the build from erroring due to the expected increase in output build size resulting from this type of build.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Reduce the number of test shards for the browser builder from 50 to 10. 50 is more than needed and can cause excessive resource usage.
This fixes the OOM errors on CI for the test job.