Add Java 17 and 25 regrtest#433
Merged
Merged
Conversation
The intention is that 17 run but not have to pass.
We expect to run this manually, not as a check on every commit.
Since at fails, for now, we don't want this to look like a blocker. But we want it present in the default branch so we can see progress to Java 17 and 25 compatibility on demand.
Member
Author
|
Ok, the way to do this seems to be a regression test that we can run manually on the CI. That way, it doesn't burn a lot of cycles automatically all the time, or disguise other failures during the time before #424 is resolved. As is too often the case with the CI, I don't seem to be able to test I've got the job itself right until it is already on |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The idea is to track which test fail without signalling that a PR is at fault.