Install-jdk.sh failing for openjdk9 and 10

jayvdb · July 2, 2019, 2:02am

Installing openjdk10
$ export JAVA_HOME=~/openjdk10
$ export PATH="$JAVA_HOME/bin:$PATH"
$ ~/bin/install-jdk.sh --target "/home/travis/openjdk10" --workspace "/home/travis/.cache/install-jdk" --feature "10" --license "GPL" --cacerts
Ignoring license option: GPL -- using GPLv2+CE by default
install-jdk.sh 2019-07-01-BETA
Variables:
  feature = 10
  license = GPL
       os = linux-x64 // os_name=linux os_arch=x64
      url = https://api.adoptopenjdk.net/v2/binary/releases/openjdk10?type=jdk&os=linux&arch=x64&release=latest&heap_size=normal&openjdk_impl=hotspot
   status = 302
Downloading JDK from https://api.adoptopenjdk.net/v2/binary/releases/openjdk10?type=jdk&os=linux&arch=x64&release=latest&heap_size=normal&openjdk_impl=hotspot...
mv: cannot stat ‘/home/travis/openjdk10/lib/security/cacerts’: No such file or directory
The command "~/bin/install-jdk.sh --target "/home/travis/openjdk10" --workspace "/home/travis/.cache/install-jdk" --feature "10" --license "GPL" --cacerts" failed and exited with 1 during .

https://travis-ci.org/coala/coala-bears/jobs/553065996

sormuras · July 2, 2019, 6:10am

Looks like the archive from AdoptOpenJDK doesn’t contain a lib/security/cacerts directory by default.

Tracking progress in https://github.com/sormuras/bach/issues/60

florianmutter · July 2, 2019, 7:05am

Is there an estimate when this will be fixed?

jayvdb · July 2, 2019, 8:55am

How is https://github.com/sormuras/bach/ related?

It has only a single job

github.com

sormuras/bach/blob/dfbefaf/.travis.yml

dist: xenial
language: java

install:
- java --version

script:
- jshell --execution local ./build.jsh

after_success:
- BACH=${TRAVIS_BUILD_DIR}/src/bach/Bach.java

- cd "${TRAVIS_BUILD_DIR}/src/demo/000-main(a)"
- java ${BACH}

- cd "${TRAVIS_BUILD_DIR}/src/demo/010-main(a,b,c)"
- java ${BACH}

- cd "${TRAVIS_BUILD_DIR}/src/demo/100-main-a-test-a,t"
- java ${BACH}

Is that in production on Travis CI? Or has my jobs been pushed to some alpha version of Travis.

nkorange · July 2, 2019, 9:27am

Same error encountered by me. Is there any solution?

sormuras · July 2, 2019, 9:52am

install-jdk.sh is hosted there, and Travis CI decided to use a copy of that script to install JDKs on-the-fly. See Java: Switch to `bach` for installing and managing JDKs · Issue #976 · travis-ci/travis-cookbooks · GitHub and related links.

Fixed install-jdk.sh already last night – Travis CI needs to update their copy the script.

/cc @BanzaiMan et al

sormuras · July 2, 2019, 10:14am

Having said that: JDK 9 and 10 “dead”, “end-of-life”, archived…

Move to JDK 11 (LTS) or 12 (until September), please.

BanzaiMan · July 2, 2019, 11:42am

I’ve deployed travis-build again.

sormuras · July 2, 2019, 11:54am

Should work now without trying to copy non-existing cacerts directory.

nkorange · July 2, 2019, 1:31pm

Still not working in my repository: https://travis-ci.org/alibaba/nacos/jobs/553146511

jayvdb · July 2, 2019, 1:46pm

There is lots of very important software that is still stuck on JDK 7 and 8, and 9 and 10, and coala wraps them. I don’t get to choose the priorities of all our dependencies, and they are usually unfunded open source.

OpenJDK 9 and 10 were working last week.
openjdk10 is listed many times on Building a Java project - Travis CI

Only oraclejdk10 is mentioned as not supported by Travis CI, and I hope that Travis CI will continue to have a pragmatic approach of continuing to provide unsupported versions long past their EOL, and not intentionally break stuff, or neglect to test and let them rot without a conscious decision that the support cost vs benefit is too high.

jayvdb · July 2, 2019, 1:50pm

Also not working for me https://travis-ci.org/coala/coala-bears/jobs/553187482 (rebuild just now)

Installing openjdk10
$ export JAVA_HOME=~/openjdk10
$ export PATH="$JAVA_HOME/bin:$PATH"
$ ~/bin/install-jdk.sh --target "/home/travis/openjdk10" --workspace "/home/travis/.cache/install-jdk" --feature "10" --license "GPL" --cacerts
Ignoring license option: GPL -- using GPLv2+CE by default
install-jdk.sh 2019-07-02-II
Variables:
  feature = 10
  license = GPL
       os = linux-x64 // os_name=linux os_arch=x64
      url = https://api.adoptopenjdk.net/v2/binary/releases/openjdk10?type=jdk&os=linux&arch=x64&release=latest&heap_size=normal&openjdk_impl=hotspot
   status = 502
Downloading JDK from https://api.adoptopenjdk.net/v2/binary/releases/openjdk10?type=jdk&os=linux&arch=x64&release=latest&heap_size=normal&openjdk_impl=hotspot...
The command "~/bin/install-jdk.sh --target "/home/travis/openjdk10" --workspace "/home/travis/.cache/install-jdk" --feature "10" --license "GPL" --cacerts" failed and exited with 8 during .

BanzaiMan · July 2, 2019, 1:55pm

It’s 502 from the server. https://travis-ci.org/coala/coala-bears/jobs/553187482#L430

jayvdb · July 2, 2019, 1:59pm

Even oraclejdk11 is 502

https://travis-ci.org/jayvdb/bach/builds/553307121

BanzaiMan · July 2, 2019, 2:02pm

We’ll have to wait for the services to be restored.

jayvdb · July 2, 2019, 2:28pm

I see there is some testing of this install script using GitHub actions ; last run at https://github.com/sormuras/bach/runs/160154663

And a quick read of the script suggests it always picks Java.net for 13+ , and always picks AdoptJDK for 12 and lower.

github.com

sormuras/bach/blob/e244aaa/install-jdk.sh#L194


        script_exit "Expected feature release number in range of 8 to ${latest_jdk}, but got: ${feature}" 3
    fi
    if [[ -d "$target" ]]; then
        script_exit "Target directory must not exist, but it does: $(du -hs '${target}')" 3
    fi
}


function determine_url() {
    # An official GA build or an archived feature? Let AdoptOpenJDK API determine the URL
    # Find API details at https://api.adoptopenjdk.net
    if [[ ${feature} -lt 13 ]]; then
        local type='jdk'
        local os_name=${os%-*}
        if [[ "$os_name" == "osx" ]]; then
          os_name='mac'
        fi
        local os_arch=${os#*-}
        local release='latest'
        local heap_size='normal'
        local openjdk_impl='hotspot'
        url="https://api.adoptopenjdk.net/v2/binary/releases/openjdk${feature}?type=${type}&os=${os_name}&arch=${os_arch}&release=${release}&heap_size=${heap_size}&openjdk_impl=${openjdk_impl}"

If so, that will not be fixed by restoring services, whatever that means.

BanzaiMan · July 2, 2019, 3:23pm

When the service on api.adoptopenjdk.net is restored, I expect the script to work. Do you have reasons to believe otherwise?

jayvdb · July 3, 2019, 2:06am

Yes, I do not expect software to work correctly unless it has been tested adequately, and these days the assurance that it was tested adequately for a purpose is initially its CI matrix and code coverage of its tests.

I’ve restarted Travis CI - Test and Deploy with Confidence right now and the API is 302 but the result is still ln: failed to create symbolic link ‘/home/travis/openjdk10/lib/security/cacerts’: No such file or directory

As I indicated in earlier posts, bach & especially install-jdk.sh are not being QA’d on all jdk versions that Travis is expected to work. The GitHub action CI mentioned above only really hits the AdoptJDK API. It does not test the majority of the logic in install-jdk.sh. It only does install-jdk.sh --dry-run, which bales out before the section of code which has the problems we are experiencing. And even if it had 100% test coverage, then it still needs additional QA for switching betwen jdk’s, as that is a completely different function point from adding a new jdk, and the ability switch jdk in an adhoc manner is sprinkled liberally through the Travis CI docs.

sormuras · July 3, 2019, 3:53am

Moved the failing call to ln into the guarded block via Don't link system CA certificates if target dir doesn't exist · sormuras/bach@c185fb8 · GitHub – version 2019-07-03 needs to be copied over to Travis CI. Again.

As stated here https://github.com/travis-ci/travis-build/pull/1347#issuecomment-385885801 and in various other places, the install-jdk.sh script was designed to just download and extract the latest-and-greatest JDK (from jdk.java.net) into a clean (CI) environment. Nothing more, nothing less.
I (still) don’t want to support more complex scenarios within the script. There are better solutions available, but I don’t know how if/whether Travis CI may make use of them: http(s) caching proxy techniques like http://www.squid-cache.org does is one option. The archived and released JDK URLs are very stable and should be pre-installed within Travis CI images, the EA releases change every 1-3 weeks. Supporting the latter was and is the main goal of install-jdk.sh.

Perhaps switching to a more complete Java Version Manager like GitHub - shyiko/jabba: (cross-platform) Java Version Manager is an option (for archived/released JDKs) for Travis CI.

Cheers,
Christian

jayvdb · July 3, 2019, 11:51am

I appreciate your predicament, and that you are trying to get your tool working according to the needs of Travis CI, GmbH.

Topic		Replies	Views
OpenJDK 10 cannot be installed Java	4	776	April 29, 2019
OpenJDK14 started to fail Java	5	763	August 24, 2020
Install of openjdk11 is failing (again) Java	30	6232	October 15, 2019
Install of openjdk11 is failing Java	10	3900	June 13, 2019
Installing of Java14 is failing Java bug	1	642	August 24, 2020

Install-jdk.sh failing for openjdk9 and 10

Related topics