Kokoro Check build failures due to NodeJS or OpenJDK installation failure about android-fhir HOT 6 OPEN

https://github.com/tj/n#custom-source would allow to overwrite URL.

But I couldn't find a more reliable NodeJS mirror e.g. on GCP.

Caching this installation is probably the way to go.

This is only worth persuing if it happens more regularly.

from android-fhir.

This is only worth persuing if it happens more regularly.

It just happened again, on https://source.cloud.google.com/results/invocations/e7f4bf2c-7a74-460e-b769-e7f9c59bd01d/targets/openhealthstack%2Fandroid-fhir%2Fgcp_ubuntu%2Fpresubmit/log, for #2298.

from android-fhir.

This is a similar problem, which I just debugged as the root cause for why #2282 has a "stuck" Kokoro: Build and Device Tests Expected — Waiting for status to be reported:

Err:4 [http://ppa.launchpad.net/openjdk-r/ppa/ubuntu](https://www.google.com/url?q=http://ppa.launchpad.net/openjdk-r/ppa/ubuntu&sa=D) xenial/main amd64 openjdk-17-jdk amd64 17~11-1~16.04~2
  Connection timed out [IP: 185.125.190.52 80]
Fetched 285 MB in 2min 13s (2,129 kB/s)
E: Failed to fetch [http://ppa.launchpad.net/openjdk-r/ppa/ubuntu/pool/main/o/openjdk-17/openjdk-17-jdk_17~11-1~16.04~2_amd64.deb](https://www.google.com/url?q=http://ppa.launchpad.net/openjdk-r/ppa/ubuntu/pool/main/o/openjdk-17/openjdk-17-jdk_17~11-1~16.04~2_amd64.deb&sa=D)  Connection timed out [IP: 185.125.190.52 80]

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?


[ID: 2992586] Command finished after 140 secs, exit value: 100

from android-fhir.

We could cache it, or save the package in a GCS Bucket that can be accessed in the script, this is the script that runs:
https://github.com/google/android-fhir/blob/master/kokoro/gcp_ubuntu/kokoro_build.sh

from android-fhir.

This (the NodeJS one) already happened AGAIN, on https://source.cloud.google.com/results/invocations/35a3c980-1b62-4a4a-88a2-daf5f0c76bfd/targets/openhealthstack%2Fandroid-fhir%2Fgcp_ubuntu%2Fpresubmit/log, for #2316 ... to me, somehow fixing this one way or another seems a fairly high priority for this project.

We could cache it, or save the package in a GCS Bucket that can be accessed in the script

Yeah. What bothers me a tiny little bit is having to cobble this together here - this kind of problem has already been solved, of course; see e.g. https://github.com/actions/cache or https://github.com/marketplace/actions/cache-apt-packages.

I'm curious if simplifying the CI infrastructure overall with #2304 wouldn't be a better way forward instead of fixing this...

But if you do happen to have bandwidth to fix this, please do!

from android-fhir.

N/A iff #2304 - but keeping open until decision if we'll do that (because if we don't, this should still be fixed).

from android-fhir.