-
Notifications
You must be signed in to change notification settings - Fork 92
test Travis-CI on JDK 17 #559
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
Conversation
scala/scala-dev@47118f1#diff-f4dff8443b496634d47500e60fd050b98480f2ee7b16635c2d5c43d131a9c398 gives us additional debugging output and now at https://app.travis-ci.com/github/scala/scala-xml/jobs/536511441 we see that the only Java.net build of 17 available is also confirmed by this by running
where the "local only" business seems to confirm that the SDKMAN folks somehow pulled it from availability |
what is |
SDKMAN needs to be updated to retrieve build 35? https://jdk.java.net/17/ |
It's strange, because looking at old Travis builds from last week, it appears SDKMAN had no trouble pulling down build 33:
|
I've reported it at https://github.com/sdkman/sdkman-candidates/issues/38 If this isn't resolved in the next few days I think we could just temporarily remove JDK 17 from the matrix until there's a fix or until JDK 17 final becomes available from the AdoptOpenJDK folks, whichever occurs first. (I'm a bit annoyed we might need to do that in multiple repos, but oh well, things happen 🤷) |
umbrella ticket on handling this org-wide (all scala/* repos): scala/scala-dev#787 |
I believe this is fixed now based on what I've seen in other repos |
Travis-CI is failing because SDKMAN isn't finding JDK 17 anymore.
Not sure what changed. Is scala/scala-dev@1a7c0e6 not right anymore?