Skip to content

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

Closed
wants to merge 2 commits into from
Closed

test Travis-CI on JDK 17 #559

wants to merge 2 commits into from

Conversation

SethTisue
Copy link
Member

@SethTisue SethTisue commented Sep 9, 2021

Travis-CI is failing because SDKMAN isn't finding JDK 17 anymore.

Not sure what changed. Is scala/scala-dev@1a7c0e6 not right anymore?

@SethTisue SethTisue marked this pull request as draft September 9, 2021 19:02
@SethTisue SethTisue self-assigned this Sep 9, 2021
@SethTisue
Copy link
Member Author

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 17.ea.3.pma; there used to also be 17.ea.28

also confirmed by this by running sdk list java locally on my Mac and I see:

               | >>> | 17.ea.28     | open    | local only | 17.ea.28-open       
               |     | 17.ea.3.pma  | open    |            | 17.ea.3.pma-open    

where the "local only" business seems to confirm that the SDKMAN folks somehow pulled it from availability

@SethTisue
Copy link
Member Author

what is 17.ea.3.pma, is it suitable for our use? my best guess is that "pma" is short for Project Panama, as in https://jdk.java.net/panama/ , and if I'm right, then no it is not suitable

@SethTisue
Copy link
Member Author

@ashawley
Copy link
Member

ashawley commented Sep 9, 2021

SDKMAN needs to be updated to retrieve build 35? https://jdk.java.net/17/

@ashawley
Copy link
Member

It's strange, because looking at old Travis builds from last week, it appears SDKMAN had no trouble pulling down build 33:

Using java version 17.ea.33-open in this shell.
openjdk version "17-ea" 2021-09-14
OpenJDK Runtime Environment (build 17-ea+33-2705)
OpenJDK 64-Bit Server VM (build 17-ea+33-2705, mixed mode, sharing)

@SethTisue
Copy link
Member Author

SethTisue commented Sep 10, 2021

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 🤷)

@SethTisue
Copy link
Member Author

umbrella ticket on handling this org-wide (all scala/* repos): scala/scala-dev#787

@SethTisue SethTisue closed this Sep 20, 2021
@SethTisue SethTisue reopened this Sep 20, 2021
@SethTisue
Copy link
Member Author

I believe this is fixed now based on what I've seen in other repos

@SethTisue SethTisue closed this Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants