| commit | 3c30964bf2efe02c82f19f47a81c066c253482a6 | [log] [tgz] |
|---|---|---|
| author | Filipe Silva <filipematossilva@gmail.com> | Fri Jan 11 07:47:04 2019 -0800 |
| committer | Copybara-Service <copybara-piper@google.com> | Fri Jan 11 07:47:36 2019 -0800 |
| tree | ffe1f3e51291994a7233cb5bb5d5a67a1925c466 | |
| parent | 5a0209ea15e061b6bef0c6c9b6b1d653855e8323 [diff] |
ci: lower memory ceiling Both https://github.com/bazelbuild/rules_typescript/pull/327 and https://github.com/bazelbuild/rules_typescript/pull/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/4a087c084cab78e610f91764db52e705aefa1814/.circleci/bazel.rc#L32-L38 this means the memory limit should be reduced. Closes #380 PiperOrigin-RevId: 228881108
diff --git a/.circleci/bazel.rc b/.circleci/bazel.rc index 75e6ee7..595b37d 100644 --- a/.circleci/bazel.rc +++ b/.circleci/bazel.rc
@@ -25,8 +25,8 @@ # 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