-
Notifications
You must be signed in to change notification settings - Fork 28.2k
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
Update Java Versions to 21 on CI #165210
base: master
Are you sure you want to change the base?
Update Java Versions to 21 on CI #165210
Conversation
…r into i163158-update-ci-java-21 resolving divergent branches
…r into i163158-update-ci-java-21 merge
@@ -1,4 +1,4 @@ | |||
org.gradle.jvmargs=-Xmx8G -XX:MaxMetaspaceSize=4G -XX:ReservedCodeCacheSize=512m -XX:+HeapDumpOnOutOfMemoryError | |||
org.gradle.jvmargs=-Xmx8G -XX:MaxMetaspaceSize=4G -XX:ReservedCodeCacheSize=512m -XX:+HeapDumpOnOutOfMemoryError -XX:+EnableDynamicAgentLoading |
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.
What problem does EnableDynamicAgentLoading fix?
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.
It's supposed to potentially get rid of a warning, but it didn't. Removed.
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.
Why delete this file?
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.
It was part of debugging a test failure related to depending on an older version of mockito that was incompatible with java 21. This lockfile can be added back without errors.
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.
and this one
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.
It was part of debugging a test failure related to depending on an older version of mockito that was incompatible with java 21. This lockfile as is causes failures. It needs to be regenerated.
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.
@gmackall do you remember what "legacy" was supposed to test? I dont remember if this test requiring is a sign that we will break users or if it was testing the legacy path of something else.
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.
No but at a glance I would guess it is a test of this code path
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy#L490
Updated java versions to 21 on CI. Monitor to see if anything breaks.
Fixes #163158
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.