-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bazel regularly crashes #13333
Comments
Looks like a worker crash. cc @larsrc-google |
Yes, that's a know issue that I fixed back in January (a607d9d). I have requested the fix to be picked into the next 4.0 release. |
//CC @philwo Every second Gerrit build crashes: [1]. Can someone help to unblock us? Is the fix a part of 4.1.0rc1? Or, otherwise, can you release hotfix version with the fix ASAP?! [1] https://gerrit-ci.gerritforge.com/view/Gerrit/job/Gerrit-bazel-java11-stable-3.4/ |
@davido Could you use |
@philwo Thanks, I've sent this CL for review: [1]. [1] https://gerrit-review.googlesource.com/c/gerrit/+/303334 |
Bazel 4.0.0 has a known worker multiplexer bug, that causes Bazel to crash spordically. The bug was fixed: [1], but the fix wasn't released yet. See this issue: [2] for more details. [1] bazelbuild/bazel@a607d9d [2] bazelbuild/bazel#13333 Change-Id: I2265c4ed7128a4b6ed259f44c5594ab717de58b0
Bump Bazel version to release 5.0.0. In this new Bazel release, --incompatible_use_toolchain_resolution_for_java_rules is flipped, that means that the build must be adapted to toolchain resolution. Specification toolchain resolution for java rules is here: [1]. Main tracking Bazel issue is here: [2]. Given that new Bazel release also added support for remote JDK 17, add support for building with remote JDK 17 to produce major byte code version 61. Note that some tests are still failing on JDK 17. This will be fixed in follow-up change. This change has a number of side effects: o Remove workaround for Bazel worker multiplexer bug, see: [3]. o Demote severity for EP bug patterns from error to warning: - DoNotMockAutoValue o Re-enable EP bug pattern: - FutureReturnValueIgnored Test Plan: To build with JDK 11 run: $ bazel build release To build with JDK 17 run: $ bazel build --config java17 release To build with JDK 11 on RBE run: $ bazel build --config=remote --remote_instance_name=<name> release To build with JDK 17 on RBE run: $ bazel build --config=remote17 --remote_instance_name=<name> release [1] https://docs.google.com/document/d/1MVbBxbKVKRJJY7DnkptHpvz7ROhyAYy4a-TZ-n7Q0r4/edit?usp=sharing [2] bazelbuild/bazel#7849 [3] bazelbuild/bazel#13333 Change-Id: Ib3b923db7bb97a24d52ae8468ad1532a970203b5
Bump Bazel version to release 5.0.0. In this new Bazel release, --incompatible_use_toolchain_resolution_for_java_rules is flipped, that means that the build must be adapted to toolchain resolution. Specification toolchain resolution for java rules is here: [1]. Main tracking Bazel issue is here: [2]. Given that new Bazel release also added support for remote JDK 17, add support for building with remote JDK 17 to produce major byte code version 61. Note that some tests are still failing on JDK 17. This will be fixed in follow-up change. This change has a number of side effects: o Remove workaround for Bazel worker multiplexer bug, see: [3]. o Demote severity for EP bug patterns from error to warning: - DoNotMockAutoValue o Re-enable EP bug pattern: - FutureReturnValueIgnored Test Plan: To build with JDK 11 run: $ bazel build release To build with JDK 17 run: $ bazel build --config java17 release To build with JDK 11 on RBE run: $ bazel build --config=remote --remote_instance_name=<name> release To build with JDK 17 on RBE run: $ bazel build --config=remote17 --remote_instance_name=<name> release [1] https://docs.google.com/document/d/1MVbBxbKVKRJJY7DnkptHpvz7ROhyAYy4a-TZ-n7Q0r4/edit?usp=sharing [2] bazelbuild/bazel#7849 [3] bazelbuild/bazel#13333 Release-Notes: skip Change-Id: Ib3b923db7bb97a24d52ae8468ad1532a970203b5
We are regularly seeing Bazel crashes on the CI:
I'm not sure how to reproduce, but the CI Job is using this arguments:
Here the last failures: [1]. The build is executing on GCloud instance.
Used Bazel version: 4.0.
Gerrit Code Review is here: https://gerrit.googlesource.com/gerrit.
[1] https://gerrit-ci.gerritforge.com/view/Gerrit/job/Gerrit-bazel-java11-stable-3.4/11/console
The text was updated successfully, but these errors were encountered: