See <https://ci-beam.apache.org/job/beam_PreCommit_Website_Cron/6911/display/redirect?page=changes>
Changes: [noreply] Bump golang.org/x/oauth2 from 0.8.0 to 0.9.0 in /sdks (#27124) ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on apache-beam-jenkins-1 (beam) in workspace <https://ci-beam.apache.org/job/beam_PreCommit_Website_Cron/ws/> The recommended git tool is: NONE No credentials specified Wiping out workspace first. Cloning the remote Git repository Using shallow clone with depth 1 Avoid fetching tags Cloning repository https://github.com/apache/beam.git > git init <https://ci-beam.apache.org/job/beam_PreCommit_Website_Cron/ws/src> > # timeout=10 Fetching upstream changes from https://github.com/apache/beam.git > git --version # timeout=10 > git --version # 'git version 2.25.1' > git fetch --no-tags --force --progress --depth=1 -- > https://github.com/apache/beam.git +refs/heads/*:refs/remotes/origin/* # > timeout=10 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # > timeout=10 > git config remote.origin.url https://github.com/apache/beam.git # timeout=10 Using shallow fetch with depth 1 Fetching upstream changes from https://github.com/apache/beam.git > git fetch --no-tags --force --progress --depth=1 -- > https://github.com/apache/beam.git +refs/heads/*:refs/remotes/origin/* > +refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/* # > timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 1db5fa5b1435cf9c6b3018c3ca007f53e231144a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 1db5fa5b1435cf9c6b3018c3ca007f53e231144a # timeout=10 Commit message: "Bump golang.org/x/oauth2 from 0.8.0 to 0.9.0 in /sdks (#27124)" > git rev-list --no-walk d998ba3475f67f66716d54f784ba46f5efa88cd7 # timeout=10 No emails were triggered. [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content SETUPTOOLS_USE_DISTUTILS=stdlib SPARK_LOCAL_IP=127.0.0.1 [EnvInject] - Variables injected successfully. [Gradle] - Launching build. [src] $ <https://ci-beam.apache.org/job/beam_PreCommit_Website_Cron/ws/src/gradlew> --continue --max-workers=8 -Dorg.gradle.jvmargs=-Xms2g -Dorg.gradle.jvmargs=-Xmx6g -Dorg.gradle.vfs.watch=false -Pdocker-pull-licenses :websitePreCommit To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.5.1/userguide/gradle_daemon.html#sec:disabling_the_daemon. Daemon will be stopped at the end of the build Configuration on demand is an incubating feature. Gradle Enterprise plugins resolution: https://plugins.gradle.org/m2 Enforcing Gradle Enterprise: https://ge.apache.org, allowUntrustedServer: false > Task :buildSrc:compileJava NO-SOURCE > Task :buildSrc:compileGroovy FROM-CACHE > Task :buildSrc:pluginDescriptors > Task :buildSrc:processResources > Task :buildSrc:classes > Task :buildSrc:jar > Task :buildSrc:assemble > Task :buildSrc:spotlessGroovy FROM-CACHE > Task :buildSrc:spotlessGroovyCheck UP-TO-DATE > Task :buildSrc:spotlessGroovyGradle FROM-CACHE > Task :buildSrc:spotlessGroovyGradleCheck UP-TO-DATE > Task :buildSrc:spotlessCheck UP-TO-DATE > Task :buildSrc:pluginUnderTestMetadata > Task :buildSrc:compileTestJava NO-SOURCE > Task :buildSrc:compileTestGroovy NO-SOURCE > Task :buildSrc:processTestResources NO-SOURCE > Task :buildSrc:testClasses UP-TO-DATE > Task :buildSrc:test NO-SOURCE > Task :buildSrc:validatePlugins FROM-CACHE > Task :buildSrc:check UP-TO-DATE > Task :buildSrc:build > Task :website:buildDockerImage Sending build context to Docker daemon 71.08MB Step 1/8 : FROM debian:stable-slim stable-slim: Pulling from library/debian Digest: sha256:b09f68bffcf9c14f3105f262e92321d05abaf48460d1f43f884325bcd4395b95 Status: Downloaded newer image for debian:stable-slim ---> aad73c16cd7c Step 2/8 : SHELL ["/bin/bash", "-o", "pipefail", "-e", "-u", "-x", "-c"] ---> Using cache ---> 74a922aadbce Step 3/8 : ENV DEBIAN_FRONTEND=noninteractive LANGUAGE=C.UTF-8 LANG=C.UTF-8 LC_ALL=C.UTF-8 LC_CTYPE=C.UTF-8 LC_MESSAGES=C.UTF-8 ---> Using cache ---> 820b6ceefcae Step 4/8 : RUN apt-get update && apt-get install -y --no-install-recommends ca-certificates curl git gnupg2 gosu lynx && apt-get autoremove -yqq --purge && apt-get clean && rm -rf /var/lib/apt/lists/* ---> Using cache ---> 0110830e2cce Step 5/8 : RUN curl -sL https://deb.nodesource.com/setup_10.x | bash - && apt-get update && apt-get install -y --no-install-recommends nodejs && apt-get autoremove -yqq --purge && apt-get clean && rm -rf /var/lib/apt/lists/* ---> Running in 36f99f2f7a6b [91m+ curl -sL https://deb.nodesource.com/setup_10.x + bash - [0m ================================================================================ ================================================================================ DEPRECATION WARNING Node.js 10.x is no longer actively supported! You will not receive security or critical stability updates for this version. You should migrate to a supported version of Node.js as soon as possible. Use the installation script that corresponds to the version of Node.js you wish to install. e.g. * https://deb.nodesource.com/setup_12.x — Node.js 12 LTS "Erbium" * https://deb.nodesource.com/setup_14.x — Node.js 14 LTS "Fermium" (recommended) * https://deb.nodesource.com/setup_16.x — Node.js 16 "Gallium" Please see https://github.com/nodejs/Release for details about which version may be appropriate for you. The NodeSource Node.js distributions repository contains information both about supported versions of Node.js and supported Linux distributions. To learn more about usage, see the repository: https://github.com/nodesource/distributions ================================================================================ ================================================================================ Continuing in 20 seconds ... ## Installing the NodeSource Node.js 10.x repo... ## Populating apt-get cache... + apt-get update Get:1 http://deb.debian.org/debian stable InRelease [147 kB] Get:2 http://deb.debian.org/debian stable-updates InRelease [52.1 kB] Get:3 http://deb.debian.org/debian-security stable-security InRelease [48.0 kB] Get:4 http://deb.debian.org/debian stable/main amd64 Packages [8904 kB] Get:5 http://deb.debian.org/debian-security stable-security/main amd64 Packages [21.8 kB] Fetched 9173 kB in 3s (2871 kB/s) Reading package lists... ## Installing packages required for setup: lsb-release... + apt-get install -y lsb-release > /dev/null 2>&1 ## Confirming "bookworm" is supported... + curl -sLf -o /dev/null 'https://deb.nodesource.com/node_10.x/dists/bookworm/Release' ## Your distribution, identified as "bookworm", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support The command '/bin/bash -o pipefail -e -u -x -c curl -sL https://deb.nodesource.com/setup_10.x | bash - && apt-get update && apt-get install -y --no-install-recommends nodejs && apt-get autoremove -yqq --purge && apt-get clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 1 > Task :website:buildDockerImage FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':website:buildDockerImage'. > Process 'command 'docker'' finished with non-zero exit value 1 * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. * Get more help at https://help.gradle.org BUILD FAILED in 1m 1s 11 actionable tasks: 5 executed, 4 from cache, 2 up-to-date Publishing build scan... https://ge.apache.org/s/rihy4ocvre6ug Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
