Install of openjdk11 is failing (again)

#1
$ ~/bin/install-jdk.sh --target "/home/travis/openjdk11" --workspace "/home/travis/.cache/install-jdk" --feature "11" --license "GPL" --cacerts

install-jdk.sh 2019-04-17

Couldn't determine a download url for 11-GPL on linux-x64

The command "~/bin/install-jdk.sh --target "/home/travis/openjdk11" --workspace "/home/travis/.cache/install-jdk" --feature "11" --license "GPL" --cacerts" failed and exited with 1 during .
4 Likes
OpenJDK 12 no longer usable
Install of openjdk11 is failing
#2

I’m also having this issue since today https://travis-ci.org/wvlet/airframe/jobs/521857989

#3

Using jdk12 also has a similar issue: OpenJDK 12 no longer usable

#4

Well ATM is fixed for OpenJDK 12. As soon as it was fixed, however, OpenJDK 11 began failing.

#5

Uploaded install-jdk.sh version 2019-04-18 a minute ago via https://github.com/sormuras/bach/commit/75cee6bae9fde21e9d8d1141ef9b873b7994ae6b

@iriberri Please update Travis’ copy of the script, again. Merci!

1 Like
#6

Thanks @sormuras!

I confirm we’ve redeployed the component needed to update our version of install-jdk.sh.

Could you restart your previously failing builds and let us know if they succeed now?

#7

Hi @dominic – I still see the “old” 2019-04-17 version being pulled-in: https://travis-ci.org/forax/pro/builds/522041100

1 Like
#8

Yes, I can second that, my build with OpenJDK 11 is also failing:

https://travis-ci.org/sirixdb/sirix/jobs/521958543

#9

Problem still there for us too.

#10

Been broken for 12+ hours now…

#11

Seconding all the reports. Looking at various builds with slightly different configurations it looks like openjdk11 is failing on trusty but passes on xenial while oraclejdk8 is having the opposite behavior i.e. fails with xenial but passes with trusty (see https://travis-ci.org/sbesson/ome-common-java/builds/522101070 vs https://travis-ci.org/sbesson/ome-common-java/builds/522101768).

While waiting for JDK deployments to get fixed across platforms, switching to xenial might be a temporary workaround for those who can afford to run against a single working environment.

#12

Hey everyone, sorry about that. I missed a step in re-deploying the required component. Could you again restart your failing builds and let us know the result? Thank you for your patience!

1 Like
#13

@dominic retested with a previously failing build and I can confirm openjdk11/trusty now works as expected.

2 Likes
#14

Hi, i can confirm that java 11 is working again.

2 Likes
#15

This is failing again, noticed it broke a couple hours ago

1 Like
#16

It looks like only Trusty is affected:

Is it an option for you to add dist: xenial to your config? Probably a good move given Trusty will be EOL at the end of the month.

Let me know what you think!

#17

Hi dominic,
I just tried openjdk11 with xenial and for me that works. What doesn’t however is openjdk12 (failed and exited with 51) and oraclejdk8 (Expected feature release number in range of 9 to 13, but got: 8) with xenial.
Maybe some more work?

#18

Installing openjdk11

$ export JAVA_HOME=~/openjdk11

$ export PATH="$JAVA_HOME/bin:$PATH"

$ ~/bin/install-jdk.sh --target “/home/travis/openjdk11” --workspace “/home/travis/.cache/install-jdk” --feature “11” --license “GPL” --cacerts

install-jdk.sh 2019-04-18

The command “~/bin/install-jdk.sh --target “/home/travis/openjdk11” --workspace “/home/travis/.cache/install-jdk” --feature “11” --license “GPL” --cacerts” failed and exited with 51 during .

2 Likes
#19

Could we use this opportunity to switch to AdoptOpenJDK distribution?

Java 11 (LTS) binary they say would be available until September 2022.

#20

Uh, isn’t Red Hat also providing support (building another distribution of the JVM)?