-
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
add JDK 14 community build #984
Comments
according to https://openjdk.java.net/projects/jdk/14/ , 2020/02/06 | | Initial Release Candidate |
on MacOS, one way to get 14 is:
|
for now, just to make sure something isn't horribly broken build-wide, I did local runs of a subset of the build on MacOS using "OpenJDK Runtime Environment (build 14-ea+14-570)" and got similar results as we're seeing on JDK 13. (on 2.12.x and 2.13.x I used |
14's release date is now just a couple months away, and I think we've learned everything we're going to learn from the 13 build, so now seems like a good time to swap in 14 for 13
so installation steps are:
I did this on all 3 behemoths then in Jenkins I renamed the two jdk13 jobs (2.12.x and 2.13.x) to jdk14 and changed the jvmVersion to 14, and also ssh'ed in to the behemoths and deleted the jdk13 workspaces then I triggered new runs and checked the logs to see if they're successfully selecting JDK 14, and they are. both jobs are running now: |
this is done results are very similar to the JDK 13 results. I did a few more test runs, excluded a few tests, reported a new Akka failure upstream, marked a repo or two as expected-to-fail, little things like that I may do some light followup work to see if we can shorten the expected-to-fail list |
https://openjdk.java.net/projects/jdk/14/ says that the "final release candidate" is coming Feb 20. I should upgrade the behemoths as soon as it's available. I'll check it on Feb 21 |
final is out. ticket: #1109 |
the action is moving to JDK 15 now: #1225 |
I'm not sure we really have the resources for this at present, and I think adding Graal is a higher priority.
Regardless, yes at some point we should replace the JDK 13 build with a JDK 14 one.
The JDK 13 ticket is #873, we should work through that one first.
Note that JDK 14 isn't LTS. (JDK 17 will be LTS.)
The text was updated successfully, but these errors were encountered: