-
Notifications
You must be signed in to change notification settings - Fork 29
Partial update to java 21 #5805
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
Conversation
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Mystery for tommorow, why on Earth do the BitBucket tests work locally but not on Circle? |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #5805 +/- ##
=============================================
- Coverage 74.44% 74.40% -0.04%
Complexity 5268 5268
=============================================
Files 365 365
Lines 19039 19046 +7
Branches 2021 2021
=============================================
- Hits 14173 14172 -1
- Misses 3903 3917 +14
+ Partials 963 957 -6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Well, the number of cache misses recorded in the circle ci job artifacts remains the same, so I guess we're good to go on that front |
This reverts commit abdf0b8.
Will keep bytecode target as Java 17 for now, looks like CircleCI image hasn't been updated on schedule yet https://discuss.circleci.com/t/linux-machine-executor-2024-q1-update/50198/2 |
If you're on Linux, recommend something like the following to switch between Java 17 and 21
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will there be another PR for Whoops, left that in by accident, ignore.
Description
Update to Java LTS 21, further pushing out our EOL.
For Java 17 Oracle EOL is Sept 2024, Eclipse Temurin has Oct 2027
For Java 21 Oracle EOL is Sept 2026, Eclipse Temurin has Sept 2029
Nonetheless, Java 21 is the next LTS version and should be better supported going forward.
We are also hoping for performance improvements https://minborgsjavapot.blogspot.com/2023/01/java-21-performance-improvements.html
Note: we have to add in a check for bitbucket testing (not prod code), looks like gson has some slightly different behaviour in Java 21
On close, will create an issue to switch the bytecode compilation to Java 21 and the CircleCI image as well.
Without the new issue, most tests on CircleCI run on Java 21, but the regression, language parsing, and localstack tests run in Java 17. The Docker image should use Java 21 and the github actions tests should use 21
Review Instructions
Builds should continue to function, qa should work after nightly deploy
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-6176
Follow-up with https://ucsc-cgl.atlassian.net/browse/SEAB-6269
Security and Privacy
Should be an improvement
Please make sure that you've checked the following before submitting your pull request. Thanks!
mvn clean install
@RolesAllowed
annotation