-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Updating JCK references for jck17 to jck17a #5780
Updating JCK references for jck17 to jck17a #5780
Conversation
Signed-off-by: Adam Farley <[email protected]>
May not be testable until the tck repo has changes as well. - Update: It turns out that this is not the case. Working on that here: https://github.com/temurin-compliance/temurin-compliance/issues/601 Update: tck repo changes complete. PR here: https://github.com/temurin-compliance/temurin-compliance/pull/602 Testing: https://ci.eclipse.org/temurin-compliance/job/Grinder/4646/ |
Grinder failed... |
New Grinder launched at: |
The new Grinder (with a valid target, good catch Shelley) has also failed. Update: Ticket raised. |
Changing title to WIP, as this change it not safe to merge until it has been tested, and it cannot be tested until this confidential Eclipse issue is resolved. |
Tested as detailed in the TCK issue. Some unit test failures, but 99% of everything passed, and nothing seemed to have trouble finding the jck17a test material. |
Thanks @karianna and @ShelleyLambert 🤓 |
Resolves #5748