-
Notifications
You must be signed in to change notification settings - Fork 246
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
Turbine Exception in 5.x versions #1013
Comments
Same for me. |
same here |
I'm only getting this issue when updating On Bazel 6.4.0, using Bzlmod. |
How do I replicate this issue? Within the repo, I've updated |
For or-tools, just check out the main branch, and run bazel -c opt test ortools/... |
I believe the issue is specifically with rules_java > 7.2.0 and Bazel < 7. See bazelbuild/rules_java#159 |
indeed, bazel7 works fine on a legacy WORKSPACE without bzlmod. |
Sorry for this. rules_java > 7.2.0 doesn't officially support Bazel 6. There shouldn't be a need to update past this version. |
It appears this is an issue with Turbine, which is part of Bazel itself. In addition, the problem only occurs when using |
This is present on all current 5.x versions (tested up to 5.3) on Bazel 6.4.0, Mac OS 13.5 (Darwin Kernel Version 22.6.0), remotejdk 17.
The error consistently does not occur on 4.5.
The error is misleading, as it is actually the
java.home
system property that's checked in the code, not the$JAVA_HOME
environment variable, so it cannot be worked around with the(host_)?action_env
flags.The text was updated successfully, but these errors were encountered: