Open
Description
#2295 (related to #2294) failed the Kokoro Check build:
[ID: 9480442] Executing command via SSH:
export KOKORO_BUILD_NUMBER="3818"
export KOKORO_JOB_NAME="openhealthstack/android-fhir/gcp_ubuntu/presubmit"
source /tmpfs/kokoro-env_vars.sh; cd /tmpfs/src/ ; chmod 755 github/android-fhir/kokoro/gcp_ubuntu/kokoro_build.sh ; PYTHON_3_VERSION="$(pyenv which python3 2> /dev/null || which python3)" ; PYTHON_2_VERSION="$(pyenv which python2 2> /dev/null || which python2)" ; if "$PYTHON_3_VERSION" -c "import psutil" ; then KOKORO_PYTHON_COMMAND="$PYTHON_3_VERSION" ; else KOKORO_PYTHON_COMMAND="$PYTHON_2_VERSION" ; fi > /dev/null 2>&1 ; echo "export KOKORO_PYTHON_COMMAND="$KOKORO_PYTHON_COMMAND"" > "$HOME/.kokoro_python_vars" ; nohup bash -c "( rm -f /tmpfs/kokoro_build_exit_code ; github/android-fhir/kokoro/gcp_ubuntu/kokoro_build.sh ; echo \${PIPESTATUS[0]} > /tmpfs/kokoro_build_exit_code ) > /tmpfs/kokoro_build.log 2>&1" > /dev/null 2>&1 & echo $! > /tmpfs/kokoro_build.pid ; source "$HOME/.kokoro_python_vars" ; "$KOKORO_PYTHON_COMMAND" /tmpfs/kokoro_log_reader.py /tmpfs/kokoro_build.log /tmpfs/kokoro_build_exit_code /tmpfs/kokoro_build.pid /tmpfs/kokoro_log_reader.pid --start_byte 0
npm WARN using --force I sure hope you know what you are doing.
/usr/local/bin/n -> /usr/local/lib/node_modules/n/bin/n
+ [email protected]
updated 1 package in 1.022s
installing : node-v16.18.0
mkdir : /usr/local/n/versions/node/16.18.0
fetch : https://nodejs.org/dist/v16.18.0/node-v16.18.0-linux-x64.tar.xz
curl: (18) transfer closed with 8144384 bytes remaining to read
xz: (stdin): Unexpected end of input
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Error: failed to download archive for 16.18.0
@omarismail94 have you seen this problem before? Often?
I suspect the cause is that that nodejs.org
is "throttling" DLs from GCP.
To avoid this, perhaps https://github.com/google/android-fhir/blob/master/kokoro/gcp_ubuntu/kokoro_build.sh could be tweaked to e.g. install NodeJS via Package Manager?
Or is it possible to do Caching on Kokoro (of e.g. the Node installation), like GitHub Actions VM can do?
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
New