-
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
java_tools tests don't pass on Windows #4165
Comments
Thanks for filing this issue. I could also repro it. I agree the problem seems to be caused by the boot class path:
Bazel propagates the jvm flags to the java launcher (good), but the
Temporarily hardcoding the absolute path in the BUILD file doesn't fix the test, but makes it fail later, giving the impression of progress. |
I added debugging info to
and I commented out the rest of the tests in that class to make it faster. The test output is:
Then I changed
Now the test output is:
Now the On both Linux and Windows, adding/removing the Yet on Linux I don't see the @cushon , do you know what could be going on? |
//CC @damienmg @meteorcloudy
Great! This raises the question, why/how the Bazel-CI is green then? Today we know (#4108), that java_tools are inherently broken on Windows: transitive class path construction compares '/'-separated paths with '\'-separated paths. And, ironically, Or are java_tools tests not active on Bazel CI for some reasons (or not active on Windows)? Inevitably, this raises another question: what other crucial unit tests are disabled/not active on Windows and why? And consequently, what other severe bugs (like #4108) are still undiscovered on Windows, that would have been discovered, when the existing Bazel unit tests would run on Bazel CI, on Windows as well? |
I'm guessing we don't run the JavacTurbineTest on Windows, since it's not accessible from @cushon has a pending internal commit that fixes this test on Windows. I'm working on fixing the |
See #4165. PiperOrigin-RevId: 177254510
See bazelbuild#4165. PiperOrigin-RevId: 177254510
Please do not assign issues to more than one team. |
@meteorcloudy is this still relevant? |
Not working on Windows Bazel QA any more. |
On bazel@HEAD:
Logs: http://paste.openstack.org/show/627381.
It seems, that
jvm_flags
doesn't have the desired effect on Windows, and-Xbootclasspath/p:<path-to-java9>
option doesn't have effect and that the default javac from Java 8 is used.The same test is passing on Linux without any issue.
The text was updated successfully, but these errors were encountered: