-
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
Custom java toolchain: Worker process returned an unparseable WorkResponse! (on Bazel 0.16.1) #6009
Comments
In 0.16.1 Line 218 in 2da247f
Overriding them in your custom toolchain will make it work with 0.16.1:
That won't be compatible with 0.17, though, since I can't reproduce the problem with 0.17rc1. I run into #5997 (comment) and #5989, but not the error you reported. How do I repro that? |
I confirm, thar the suggested workaround works as expected on 0.16.1, but that breaks 0.17.rc1, because now I get:
Is there a way to import things conditionally? Reproducer: https://gerrit-review.googlesource.com/c/gerrit/+/194045 |
Right. I'm not aware of a conditional import mechanism. You could define different toolchains for 0.16 and 0.17, or inline those JVM flags instead of using the constant. Is the core dump you mentioned seeing with 0.17rc1 in your original comment reproducible, or was that a transient failure? |
[...]
Never mind, I re-downloaded 0.17rc1 and confirmed it works with restrictions, that you've mentioned. Apparently I had the old 0.17rc1 download, that was re-cut recently. Sorry that I messed that up. |
An alternative workaround should then be to respect https://docs.bazel.build/versions/master/install-compile-source.html and use JDK 8. I can confirm that this works: I just built 0.16.1 successfully on openSUSE Leap 15.0 with JDK 8. (I uninstalled JDKs 10 and 11 as openSUSE doesn't have update-java-alternatives and changing a handful of alternatives with update-alternatives seems too much hassle.) |
Trying to use custom
java_toolchain
is failing on latest released Bazel version (0.16.1):On unreleased 0.17rc1 there is another error:
On Bazel@HEAD (2894b30) it seems to work.
Reproducer: https://gerrit-review.googlesource.com/c/gerrit/+/194045.
The text was updated successfully, but these errors were encountered: