Skip to content

Commit

Permalink
ci: lower memory ceiling
Browse files Browse the repository at this point in the history
Both bazelbuild/rules_typescript#327 and bazelbuild/rules_typescript#378 have circleci `test` jobs being killed:
```
Server terminated abruptly (error code: 14, error message: '', log file: '/home/circleci/.cache/bazel/_bazel_circleci/cced162ff126e466524550c57f0d7df5/server/jvm.out')
```

According to the note in https://github.com/bazelbuild/rules_typescript/blob/3671b8d5b6f5731e191098b6d5243c44f474c0da/.circleci/bazel.rc#L32-L38 this means the memory limit should be reduced.

Closes bazel-contrib#380

PiperOrigin-RevId: 228881108
  • Loading branch information
filipesilva authored and Keen Yee Liau committed Jan 12, 2019
1 parent 3671b8d commit c16522d
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,8 @@ build --experimental_repository_cache=/home/circleci/bazel_repository_cache

# Workaround https://github.com/bazelbuild/bazel/issues/3645
# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
# Limit Bazel to consuming 2560K of RAM
build --local_resources=2560,1.0,1.0
# Limit Bazel to consuming 2360K of RAM
build --local_resources=2360,1.0,1.0
# Also limit Bazel's own JVM heap to stay within our 4G container limit
startup --host_jvm_args=-Xmx3g
# Since the default CircleCI container has only 4G, limiting the memory
Expand Down

0 comments on commit c16522d

Please sign in to comment.