See 
<https://ci-beam.apache.org/job/beam_PostCommit_Website_Test/8238/display/redirect>

Changes:


------------------------------------------
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on websites1 (git-websites svn-websites) in workspace 
<https://ci-beam.apache.org/job/beam_PostCommit_Website_Test/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_PostCommit_Website_Test/ws/src> # 
 > timeout=10
Fetching upstream changes from https://github.com/apache/beam.git
 > git --version # timeout=10
 > git --version # 'git version 2.17.1'
 > git fetch --no-tags --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 --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 0822ab49697d3cb0f3f0b069e64c9571b848b7e2 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0822ab49697d3cb0f3f0b069e64c9571b848b7e2 # timeout=10
Commit message: "Initial implementation of QuotaEvent (#27078)"
 > git rev-list --no-walk 0132967e751ac3d012006ef4fc61b304a5b505f4 # timeout=10
First time build. Skipping changelog.
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_PostCommit_Website_Test/ws/src/gradlew> 
--continue --max-workers=8 -Dorg.gradle.jvmargs=-Xms2g 
-Dorg.gradle.jvmargs=-Xmx6g -Dorg.gradle.vfs.watch=false -Pdocker-pull-licenses 
:website:testWebsite -PdisableExternal=false
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
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile:
#1 transferring dockerfile: 2.56kB done
#1 DONE 0.4s

#2 [internal] load .dockerignore
#2 transferring context: 2B done
#2 DONE 0.5s

#3 [internal] load metadata for docker.io/library/debian:stable-slim
#3 DONE 1.6s

#4 [1/6] FROM 
docker.io/library/debian:stable-slim@sha256:b09f68bffcf9c14f3105f262e92321d05abaf48460d1f43f884325bcd4395b95
#4 resolve 
docker.io/library/debian:stable-slim@sha256:b09f68bffcf9c14f3105f262e92321d05abaf48460d1f43f884325bcd4395b95
#4 resolve 
docker.io/library/debian:stable-slim@sha256:b09f68bffcf9c14f3105f262e92321d05abaf48460d1f43f884325bcd4395b95
 0.5s done
#4 DONE 0.5s

#5 [2/6] 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/*
#5 CACHED

#6 [3/6] 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/*
#6 0.926 + curl -sL https://deb.nodesource.com/setup_10.x
#6 0.926 + bash -
#6 1.011 
#6 1.011 
================================================================================
#6 1.011 
================================================================================
#6 1.011 
#6 1.011                               DEPRECATION WARNING                      
      
#6 1.011 
#6 1.011   Node.js 10.x is no longer actively supported!
#6 1.011 
#6 1.011   You will not receive security or critical stability updates for this 
version.
#6 1.011 
#6 1.011   You should migrate to a supported version of Node.js as soon as 
possible.
#6 1.011   Use the installation script that corresponds to the version of 
Node.js you
#6 1.011   wish to install. e.g.
#6 1.011 
#6 1.011    * https://deb.nodesource.com/setup_12.x — Node.js 12 LTS "Erbium"
#6 1.011    * https://deb.nodesource.com/setup_14.x — Node.js 14 LTS "Fermium" 
(recommended)
#6 1.011    * https://deb.nodesource.com/setup_16.x — Node.js 16 "Gallium"
#6 1.011 
#6 1.011   Please see https://github.com/nodejs/Release for details about which
#6 1.011   version may be appropriate for you.
#6 1.011 
#6 1.011   The NodeSource Node.js distributions repository contains
#6 1.011   information both about supported versions of Node.js and supported 
Linux
#6 1.011   distributions. To learn more about usage, see the repository:
#6 1.011     https://github.com/nodesource/distributions
#6 1.011 
#6 1.011 
================================================================================
#6 1.011 
================================================================================
#6 1.011 
#6 1.011 Continuing in 20 seconds ...
#6 1.011 
#6 21.01 
#6 21.01 ## Installing the NodeSource Node.js 10.x repo...
#6 21.01 
#6 21.02 
#6 21.02 ## Populating apt-get cache...
#6 21.02 
#6 21.02 + apt-get update
#6 21.06 Get:1 http://deb.debian.org/debian stable InRelease [147 kB]
#6 21.21 Get:2 http://deb.debian.org/debian stable-updates InRelease [52.1 kB]
#6 21.21 Get:3 http://deb.debian.org/debian-security stable-security InRelease 
[48.0 kB]
#6 21.31 Get:4 http://deb.debian.org/debian stable/main amd64 Packages [8904 kB]
#6 21.43 Get:5 http://deb.debian.org/debian-security stable-security/main amd64 
Packages [21.8 kB]
#6 22.38 Fetched 9173 kB in 1s (6862 kB/s)
#6 22.38 Reading package lists...
#6 22.89 
#6 22.89 ## Installing packages required for setup: lsb-release...
#6 22.89 
#6 22.89 + apt-get install -y lsb-release > /dev/null 2>&1
#6 24.92 
#6 24.92 ## Confirming "bookworm" is supported...
#6 24.92 
#6 24.92 + curl -sLf -o /dev/null 
'https://deb.nodesource.com/node_10.x/dists/bookworm/Release'
#6 26.01 
#6 26.01 ## 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
#6 26.01 
#6 ERROR: process "/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/*" did not complete successfully: exit code: 1
------
 > [3/6] 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/*:
#6 22.89 ## Installing packages required for setup: lsb-release...
#6 22.89 
#6 22.89 + apt-get install -y lsb-release > /dev/null 2>&1
#6 24.92 
#6 24.92 ## Confirming "bookworm" is supported...
#6 24.92 
#6 24.92 + curl -sLf -o /dev/null 
'https://deb.nodesource.com/node_10.x/dists/bookworm/Release'
#6 26.01 
#6 26.01 ## 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
#6 26.01 
------
Dockerfile:46
--------------------
  45 |     # Install node environment
  46 | >>> RUN curl -sL https://deb.nodesource.com/setup_10.x | bash - \
  47 | >>>     && apt-get update \
  48 | >>>     && apt-get install -y --no-install-recommends \
  49 | >>>         nodejs \
  50 | >>>     && apt-get autoremove -yqq --purge \
  51 | >>>     && apt-get clean \
  52 | >>>     && rm -rf /var/lib/apt/lists/*
  53 |     
--------------------
ERROR: failed to solve: process "/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/*" did not complete successfully: exit 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 40s
11 actionable tasks: 5 executed, 4 from cache, 2 up-to-date

Publishing build scan...
https://ge.apache.org/s/z377lidgpqgjc

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]

Reply via email to