-
Notifications
You must be signed in to change notification settings - Fork 39
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
Disable failing JDK 20-ea build for now #419
Conversation
The build fails due to openjdk/jdk20@2cb64a7; the upcoming Error Prone release includes a fix for this: google/error-prone@df033f0.
Looks good. No mutations were possible for these changes. |
.github/workflows/build.yaml
Outdated
jdk: 20-ea | ||
distribution: zulu | ||
experimental: true | ||
# XXX: Reenable this build after upgrading to Error Prone 2.17. |
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.
Based on some googling I think "re-enable" is a lot more common to use than "reenable". WDYT?
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 strong opinion 🙃
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.
We can circumvent this oddity by using Reactivate
instead, as suggested here. 😄
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.
LGTM. Maybe s/fix/workaround
in the suggested commit message in line with the wording of the commit in error prone?
.github/workflows/build.yaml
Outdated
jdk: 20-ea | ||
distribution: zulu | ||
experimental: true | ||
# XXX: Reenable this build after upgrading to Error Prone 2.17. |
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.
We can circumvent this oddity by using Reactivate
instead, as suggested here. 😄
Looks good. No mutations were possible for these changes. |
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.
Maybe
s/fix/workaround
in the suggested commit message in line with the wording of the commit in error prone?
Changed it. Tweaks LGTM. Approving assuming build passes ✔️
The enable terminology is used more often I would say, so went with the hyphen option :). |
See the analysis in #418 for context.
Suggested commit message: