Graham/angular-cli
1
0
Fork 0
mirror of https://github.com/angular/angular-cli.git synced 2025-05-16 10:33:43 +08:00
Code Issues Packages Projects Releases Wiki Activity

ci: change bazel to use XL container resources

Browse Source 
We are limiting Bazel to consuming resources that fit in CircleCI "medium" class but Circle steps are configured to use "xlarge" containers

aacb98d85b/.circleci/bazel.rc (L13-L17)

Changing the contain to "medium" causes `Stream closed` failures
This commit is contained in:
Alan Agius 2020-08-18 14:57:15 +02:00
parent 3e76676fe1
commit 1be09a03dd
2 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.circleci/bazel.rc
View File

@ -12,10 +12,10 @@ test --test_tag_filters=-manual
# Workaround https://github.com/bazelbuild/bazel/issues/3645
# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
# Limit Bazel to consuming resources that fit in CircleCI "medium" class which is the default:
# Limit Bazel to consuming resources that fit in CircleCI "xlarge" class
# https://circleci.com/docs/2.0/configuration-reference/#resource_class
build --local_ram_resources=3072
build --local_cpu_resources=2
build --local_cpu_resources=8
build --local_ram_resources=14336
# More details on failures
build --verbose_failures=true

1
.circleci/config.yml
View File

@ -260,6 +260,7 @@ jobs:
steps:
- custom_attach_workspace
- install_python
- run: sudo cp .circleci/bazel.rc /etc/bazel.bazelrc
- run:
command: yarn bazel:integration
no_output_timeout: 20m