Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Skipping these steps for GraalVM sounds good.
I'm realizing that there isn't a lot of overlap between the steps that we want to do for GraalVM and other JDKs--I think all of the steps here happen on other JDKs, or on GraalVM, but not both.
What do you think about adding a separate entry under
jobs:
for the GraalVM test, isntead of adding it to the matrix with the other JDKs and avoiding all of the checks forjava == graal
andjava != graal
?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.
FTR: This was done in #1055. (I'll close this PR.)