can not build with server terminated message.
1 Answers
The most common cause I've seen for this kind of thing (can't say for sure without the jvm.out) is running out of memory which results in the OOM killer terminating the bazel server process. Between the bazel server process and a bunch of C++ compilations in parallel, it's easy to run out. Using a lower --jobs is the most direct way to limit that. --local_ram_resources will help in theory, but bazel doesn't have a very good idea how much RAM each compilation command uses so it's very approximate.
Related