-
Notifications
You must be signed in to change notification settings - Fork 59
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
JDK 9+ support #127
Comments
I pushed PR #128 to fix this issue. |
Thanks ! This fixes the compilation problem, but I see issues during benchmark executions for JDK9 and JDK11. Let’s keep that issue open until we have fixed all of these and added the Travis check on JDK11. |
Sounds good to me to close. |
I am very surprised that it works on Travis, because locally (on MacOS) I hit an error in a static initializer on JDK11 for Spark benchmarks (everything fine on JDK8, JDK9 and JDK10).
Are you 100% that the Travis gate runs the benchmark on the correct JDK ? It's not sufficient to have |
I have pushed one more commit (335820a) to the However, we test only the default Java installation on MacOS (seems to be Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)). We should probably test multiple JDKs there too. |
Thanks for the extra check. Indeed the default I hit the bug with the following version :
|
I think we could safely close the issue if we are confident that everything works fine at least on Linux from JDK8 up until the latest dev JDK. I see that Travis supports |
Related to #244 |
We should make sure that the suite works well with the the most recent JDK versions.
And the travis gate should include a JDK11 test and maybe newer if possible.
I currently see that there is an issue building the suite with JDK11 :
The text was updated successfully, but these errors were encountered: