You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@beam.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2022/09/14 04:22:45 UTC
Build failed in Jenkins: beam_Publish_Beam_SDK_Snapshots #3888
See <https://ci-beam.apache.org/job/beam_Publish_Beam_SDK_Snapshots/3888/display/redirect>
Changes:
------------------------------------------
[...truncated 259.44 KB...]
print(
"ERROR: Can not execute `setup.py` since setuptools is not available in "
"the build environment.",
file=sys.stderr,
)
sys.exit(1)
__file__ = %r
sys.argv[0] = __file__
if os.path.exists(__file__):
filename = __file__
with tokenize.open(__file__) as f:
setup_py_code = f.read()
else:
filename = "<auto-generated setuptools caller>"
setup_py_code = "from setuptools import setup; setup()"
exec(compile(setup_py_code, filename, "exec"))
'"'"''"'"''"'"' % ('"'"'/tmp/pip-req-build-mqaspog5/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' egg_info --egg-base /tmp/pip-pip-egg-info-pbov4n_2
[0m[91m cwd: /tmp/pip-req-build-mqaspog5/
[0m Preparing metadata (setup.py): finished with status 'error'
[91merror: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
[0mThe command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
> Task :sdks:python:container:py38:docker FAILED
> Task :sdks:python:container:py37:docker
---> Running in 886b4de00320
Removing intermediate container 886b4de00320
---> a4fdd2fe72c7
Step 12/32 : RUN ccache --set-config=sloppiness=file_macro && ccache --set-config=hash_dir=false
---> Running in b74a91c8fab0
Removing intermediate container b74a91c8fab0
---> e3b10d550e3c
Step 13/32 : COPY target/apache-beam.tar.gz /opt/apache/beam/tars/
---> 7397b56e33ec
Step 14/32 : RUN pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]
---> Running in f9eb306ba229
Using pip 22.2.2 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
Processing /opt/apache/beam/tars/apache-beam.tar.gz
Preparing metadata (setup.py): started
[91m Running command python setup.py egg_info
[0m[91m Traceback (most recent call last):
[0m[91m File "<string>", line 36, in <module>
[0m[91m File "<pip-setuptools-caller>", line 34, in <module>
[0m[91m File "/tmp/pip-req-build-6ieu_ha_/setup.py", line 169, in <module>
[0m[91m generate_protos_first()
[0m[91m File "/tmp/pip-req-build-6ieu_ha_/setup.py", line 139, in generate_protos_first
[0m[91m gen_protos.generate_proto_files()
[0m[91m File "/tmp/pip-req-build-6ieu_ha_/gen_protos.py", line 476, in generate_proto_files
[0m[91m raise RuntimeError(error_msg)
[0m[91m RuntimeError: Not in apache git tree, unable to find proto definitions.
[0m[91m error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
[0m[91m full command: /usr/local/bin/python -c '
exec(compile('"'"''"'"''"'"'
# This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
#
# - It imports setuptools before invoking setup.py, to enable projects that directly
# import from `distutils.core` to work with newer packaging standards.
# - It provides a clear error message when setuptools is not installed.
# - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
# setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
# manifest_maker: standard file '"'"'-c'"'"' not found".
# - It generates a shim setup.py, for handling setup.cfg-only projects.
import os, sys, tokenize
try:
import setuptools
except ImportError as error:
print(
"ERROR: Can not execute `setup.py` since setuptools is not available in "
"the build environment.",
file=sys.stderr,
)
sys.exit(1)
__file__ = %r
sys.argv[0] = __file__
if os.path.exists(__file__):
filename = __file__
with tokenize.open(__file__) as f:
setup_py_code = f.read()
else:
filename = "<auto-generated setuptools caller>"
setup_py_code = "from setuptools import setup; setup()"
exec(compile(setup_py_code, filename, "exec"))
'"'"''"'"''"'"' % ('"'"'/tmp/pip-req-build-6ieu_ha_/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' egg_info --egg-base /tmp/pip-pip-egg-info-69ykpa0b
[0m[91m cwd: /tmp/pip-req-build-6ieu_ha_/
[0m Preparing metadata (setup.py): finished with status 'error'
[91merror: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
[0m
> Task :sdks:python:container:py39:docker FAILED
---> Running in 58c97c934e21
Removing intermediate container 58c97c934e21
---> e95b8bf9354e
Step 12/32 : RUN ccache --set-config=sloppiness=file_macro && ccache --set-config=hash_dir=false
---> Running in 9af16e672030
Removing intermediate container 9af16e672030
---> 011f9756bf96
Step 13/32 : COPY target/apache-beam.tar.gz /opt/apache/beam/tars/
---> 909ffaf303a2
Step 14/32 : RUN pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]
---> Running in 7a7e09a059f5
Using pip 22.2.2 from /usr/local/lib/python3.9/site-packages/pip (python 3.9)
Processing /opt/apache/beam/tars/apache-beam.tar.gz
Preparing metadata (setup.py): started
[91m Running command python setup.py egg_info
[0m[91m Traceback (most recent call last):
[0m[91m File "<string>", line 2, in <module>
[0m[91m File "<pip-setuptools-caller>", line 34, in <module>
[0m[91m File "/tmp/pip-req-build-kj1nl1eu/setup.py", line 169, in <module>
[0m[91m generate_protos_first()
[0m[91m File "/tmp/pip-req-build-kj1nl1eu/setup.py", line 139, in generate_protos_first
[0m[91m gen_protos.generate_proto_files()
[0m[91m File "/tmp/pip-req-build-kj1nl1eu/gen_protos.py", line 476, in generate_proto_files
[0m[91m raise RuntimeError(error_msg)
[0m[91m RuntimeError: Not in apache git tree, unable to find proto definitions.
[0m[91m error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
[0m[91m full command: /usr/local/bin/python -c '
exec(compile('"'"''"'"''"'"'
# This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
#
# - It imports setuptools before invoking setup.py, to enable projects that directly
# import from `distutils.core` to work with newer packaging standards.
# - It provides a clear error message when setuptools is not installed.
# - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
# setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
# manifest_maker: standard file '"'"'-c'"'"' not found".
# - It generates a shim setup.py, for handling setup.cfg-only projects.
import os, sys, tokenize
try:
import setuptools
except ImportError as error:
print(
"ERROR: Can not execute `setup.py` since setuptools is not available in "
"the build environment.",
file=sys.stderr,
)
sys.exit(1)
__file__ = %r
sys.argv[0] = __file__
if os.path.exists(__file__):
filename = __file__
with tokenize.open(__file__) as f:
setup_py_code = f.read()
else:
filename = "<auto-generated setuptools caller>"
setup_py_code = "from setuptools import setup; setup()"
exec(compile(setup_py_code, filename, "exec"))
'"'"''"'"''"'"' % ('"'"'/tmp/pip-req-build-kj1nl1eu/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' egg_info --egg-base /tmp/pip-pip-egg-info-o2qtu3ul
[0m[91m cwd: /tmp/pip-req-build-kj1nl1eu/
[0m Preparing metadata (setup.py): finished with status 'error'
[91merror: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
[0mThe command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
> Task :sdks:python:container:py37:docker FAILED
The command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
FAILURE: Build completed with 3 failures.
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py38:docker'.
> 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.
==============================================================================
2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py39:docker'.
> 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.
==============================================================================
3: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py37:docker'.
> 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
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 3 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
BUILD FAILED in 9m 13s
156 actionable tasks: 119 executed, 25 from cache, 12 up-to-date
Publishing build scan...
https://gradle.com/s/yscvy32sx25fw
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org
Jenkins build is back to normal : beam_Publish_Beam_SDK_Snapshots #3892
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://ci-beam.apache.org/job/beam_Publish_Beam_SDK_Snapshots/3892/display/redirect?page=changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org
Build failed in Jenkins: beam_Publish_Beam_SDK_Snapshots #3891
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://ci-beam.apache.org/job/beam_Publish_Beam_SDK_Snapshots/3891/display/redirect?page=changes>
Changes:
[noreply] Exclude protobuf 3.20.2 (#23226)
[noreply] Fix IllegalStateException in StorageApiWriteUnshardedRecords error
------------------------------------------
[...truncated 76.84 KB...]
bafdbe68e4ae: Layer already exists
a13c519c6361: Layer already exists
6800c6b3708c: Pushed
aebe719137c8: Pushed
> Task :sdks:java:container:java11:dockerPushLatest
> Task :sdks:java:container:java11:dockerTagsPush
> Task :release:go-licenses:py:dockerRun
go: added github.com/apache/beam/sdks/v2 v2.41.0
go: added github.com/golang/protobuf v1.5.2
go: added github.com/nightlyone/lockfile v1.0.0
go: added golang.org/x/net v0.0.0-20220624214902-1bab6f366d9e
go: added golang.org/x/sys v0.0.0-20220624220833-87e55d714810
go: added golang.org/x/text v0.3.7
go: added google.golang.org/genproto v0.0.0-20220714211235-042d03aeabc9
go: added google.golang.org/grpc v1.48.0
go: added google.golang.org/protobuf v1.28.0
+ go-licenses save github.com/apache/beam/sdks/v2/python/container --save_path=/output/licenses
W0914 16:15:59.726671 28 library.go:94] "golang.org/x/sys/unix" contains non-Go code that can't be inspected for further dependencies:
/go/pkg/mod/golang.org/x/sys@v0.0.0-20220624220833-87e55d714810/unix/asm_linux_amd64.s
> Task :sdks:java:container:java17:dockerTagLatest
> Task :release:go-licenses:py:dockerRun
+ go-licenses csv github.com/apache/beam/sdks/v2/python/container
+ tee /output/licenses/list.csv
> Task :sdks:java:container:java17:dockerPushLatest
The push refers to repository [gcr.io/apache-beam-testing/beam-sdk/beam_java17_sdk]
aa344fc3bbe3: Preparing
8cf3c71e62ae: Preparing
74a82aa12850: Preparing
a4193c546ecd: Preparing
beceb009d41a: Preparing
12fb521470a0: Preparing
b29d30abd8ee: Preparing
7706e59a15d8: Preparing
80505724f6c5: Preparing
582b17ab2a39: Preparing
40fc3a82ea16: Preparing
7f200064166e: Preparing
da02c78777a1: Preparing
6800c6b3708c: Preparing
aebe719137c8: Preparing
3bc383470c05: Preparing
e93827457889: Preparing
08fa02ce37eb: Preparing
a037458de4e0: Preparing
bafdbe68e4ae: Preparing
a13c519c6361: Preparing
b29d30abd8ee: Waiting
582b17ab2a39: Waiting
7f200064166e: Waiting
40fc3a82ea16: Waiting
80505724f6c5: Waiting
aebe719137c8: Waiting
da02c78777a1: Waiting
6800c6b3708c: Waiting
08fa02ce37eb: Waiting
bafdbe68e4ae: Waiting
a13c519c6361: Waiting
12fb521470a0: Waiting
a037458de4e0: Waiting
7706e59a15d8: Waiting
e93827457889: Waiting
a4193c546ecd: Layer already exists
8cf3c71e62ae: Layer already exists
aa344fc3bbe3: Layer already exists
74a82aa12850: Layer already exists
beceb009d41a: Layer already exists
7706e59a15d8: Layer already exists
12fb521470a0: Layer already exists
80505724f6c5: Layer already exists
582b17ab2a39: Layer already exists
b29d30abd8ee: Layer already exists
aebe719137c8: Layer already exists
40fc3a82ea16: Layer already exists
da02c78777a1: Layer already exists
6800c6b3708c: Layer already exists
7f200064166e: Layer already exists
e93827457889: Layer already exists
a037458de4e0: Layer already exists
3bc383470c05: Layer already exists
bafdbe68e4ae: Layer already exists
08fa02ce37eb: Layer already exists
a13c519c6361: Layer already exists
latest: digest: sha256:aad4e796989db3873a8ddb55d7a74c7fbae66b4f7a7658bf8c5d8565b3dddde1 size: 4729
> Task :sdks:java:container:java17:dockerTagsPush
> Task :release:go-licenses:py:dockerRun
W0914 16:16:04.184102 190 library.go:94] "golang.org/x/sys/unix" contains non-Go code that can't be inspected for further dependencies:
/go/pkg/mod/golang.org/x/sys@v0.0.0-20220624220833-87e55d714810/unix/asm_linux_amd64.s
github.com/apache/beam/sdks/v2/go/pkg/beam,https://github.com/apache/beam/blob/sdks/v2.41.0/sdks/go/README.md,Apache-2.0
github.com/apache/beam/sdks/v2/python/container,https://github.com/apache/beam/blob/sdks/v2.41.0/sdks/LICENSE,Apache-2.0
github.com/golang/protobuf,https://github.com/golang/protobuf/blob/v1.5.2/LICENSE,BSD-3-Clause
github.com/nightlyone/lockfile,https://github.com/nightlyone/lockfile/blob/v1.0.0/LICENSE,MIT
golang.org/x/net,https://cs.opensource.google/go/x/net/+/1bab6f36:LICENSE,BSD-3-Clause
golang.org/x/sys,https://cs.opensource.google/go/x/sys/+/87e55d71:LICENSE,BSD-3-Clause
golang.org/x/text,https://cs.opensource.google/go/x/text/+/v0.3.7:LICENSE,BSD-3-Clause
google.golang.org/genproto/googleapis/rpc/status,https://github.com/googleapis/go-genproto/blob/042d03aeabc9/LICENSE,Apache-2.0
google.golang.org/grpc,https://github.com/grpc/grpc-go/blob/v1.48.0/LICENSE,Apache-2.0
google.golang.org/protobuf,https://github.com/protocolbuffers/protobuf-go/blob/v1.28.0/LICENSE,BSD-3-Clause
+ chmod -R a+w /output/licenses
> Task :release:go-licenses:py:createLicenses
> Task :sdks:python:container:py38:copyGolangLicenses
> Task :sdks:python:container:py37:copyGolangLicenses
> Task :sdks:python:container:py38:dockerClean UP-TO-DATE
> Task :sdks:python:container:py39:copyDockerfileDependencies
> Task :sdks:python:container:py39:copyGolangLicenses
> Task :sdks:python:container:py37:dockerPrepare
> Task :sdks:python:container:py39:copyLauncherDependencies
> Task :sdks:python:container:py38:dockerPrepare
> Task :sdks:python:container:py39:copyLicenseScripts
> Task :sdks:python:container:py39:copyLicenses
> Task :sdks:python:container:py39:dockerClean UP-TO-DATE
> Task :sdks:python:container:py39:dockerPrepare
> Task :sdks:python:container:py37:docker
> Task :sdks:python:container:py38:docker
> Task :sdks:python:container:py39:docker
> Task :sdks:python:container:py37:dockerTag66bbee84ed477d86008905646e68b100591b6f78
> Task :sdks:python:container:py38:docker
Removing intermediate container a06250706b58
---> 9a6fa76235d0
Successfully built 9a6fa76235d0
Successfully tagged gcr.io/apache-beam-testing/beam-sdk/beam_python3.8_sdk:2.43.0.dev
> Task :sdks:python:container:py38:dockerTag66bbee84ed477d86008905646e68b100591b6f78
> Task :sdks:python:container:py39:dockerTag66bbee84ed477d86008905646e68b100591b6f78
> Task :sdks:python:container:py37:dockerPush66bbee84ed477d86008905646e68b100591b6f78
> Task :sdks:python:container:py38:dockerPush66bbee84ed477d86008905646e68b100591b6f78
> Task :sdks:python:container:py39:dockerPush66bbee84ed477d86008905646e68b100591b6f78
> Task :sdks:python:container:py37:dockerTagLatest
> Task :sdks:python:container:py37:dockerPushLatest
The push refers to repository [gcr.io/apache-beam-testing/beam-sdk/beam_python3.7_sdk]
b2edd076ff4e: Preparing
013e5b5519ae: Preparing
b6a147696fd5: Preparing
dde25062f20d: Preparing
669a27b3b60f: Preparing
5961814f219c: Preparing
a1e56a38f273: Preparing
3fe168f9e662: Preparing
3a51b96d6087: Preparing
cd1fea99cd74: Preparing
5b0e739d22d5: Preparing
d482625edabf: Preparing
316f69808147: Preparing
2b96f8a6951a: Preparing
4f604838ab6d: Preparing
cd901c6d1541: Preparing
e87ec86b1847: Preparing
6966fb7c59ef: Preparing
b78efdac8138: Preparing
669a27b3b60f: Waiting
bcc8223cbebf: Preparing
a24f9e96a54c: Preparing
54b354c15c5a: Preparing
5961814f219c: Waiting
b9fcb0f781e4: Preparing
cd1fea99cd74: Waiting
e87ec86b1847: Waiting
a1e56a38f273: Waiting
d482625edabf: Waiting
5b0e739d22d5: Waiting
b9fcb0f781e4: Waiting
3fe168f9e662: Waiting
a24f9e96a54c: Waiting
3a51b96d6087: Waiting
6966fb7c59ef: Waiting
316f69808147: Waiting
b78efdac8138: Waiting
54b354c15c5a: Waiting
cd901c6d1541: Waiting
dde25062f20d: Waiting
4f604838ab6d: Waiting
bcc8223cbebf: Waiting
2b96f8a6951a: Waiting
b2edd076ff4e: Layer already exists
013e5b5519ae: Layer already exists
b6a147696fd5: Layer already exists
669a27b3b60f: Layer already exists
dde25062f20d: Layer already exists
5961814f219c: Layer already exists
3fe168f9e662: Layer already exists
3a51b96d6087: Layer already exists
a1e56a38f273: Layer already exists
cd1fea99cd74: Layer already exists
5b0e739d22d5: Layer already exists
d482625edabf: Layer already exists
316f69808147: Layer already exists
2b96f8a6951a: Layer already exists
4f604838ab6d: Layer already exists
cd901c6d1541: Layer already exists
e87ec86b1847: Layer already exists
6966fb7c59ef: Layer already exists
b78efdac8138: Layer already exists
bcc8223cbebf: Layer already exists
a24f9e96a54c: Layer already exists
54b354c15c5a: Layer already exists
b9fcb0f781e4: Layer already exists
latest: digest: sha256:847c5648cf18f9c2514dde03daff822237390ea83f903f46f8e1ee984e8c07fe size: 5156
> Task :sdks:python:container:py37:dockerTagsPush
> Task :sdks:python:container:py38:dockerPush66bbee84ed477d86008905646e68b100591b6f78
9202567112d8: Pushed
66bbee84ed477d86008905646e68b100591b6f78: digest: sha256:7cc79db5e83eb1af67ecc3582f81cf5b3a7426706697ed587cb71db75a63d630 size: 5156
> Task :sdks:python:container:py38:dockerTagLatest
> Task :sdks:python:container:py38:dockerPushLatest
> Task :sdks:python:container:py38:dockerTagsPush
> Task :sdks:python:container:py39:dockerTagLatest
> Task :sdks:python:container:py39:dockerPushLatest
> Task :sdks:python:container:py39:dockerTagsPush
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':sdks:java:container:java8:docker'.
> 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
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 3 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
BUILD FAILED in 16m 36s
164 actionable tasks: 127 executed, 25 from cache, 12 up-to-date
Publishing build scan...
https://gradle.com/s/quuj52k5ojpse
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org
Build failed in Jenkins: beam_Publish_Beam_SDK_Snapshots #3890
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://ci-beam.apache.org/job/beam_Publish_Beam_SDK_Snapshots/3890/display/redirect?page=changes>
Changes:
[noreply] Publish results of JMH benchmark runs (Java SDK) to InfluxDB (part of
------------------------------------------
[...truncated 81.15 KB...]
7c255a74d815: Waiting
553c80416999: Waiting
107f7a71b278: Waiting
adef16b9ec4f: Waiting
d690f8420aca: Waiting
30320913a640: Waiting
9a3de0861b46: Layer already exists
c44b8eb36b87: Layer already exists
81b46be4e8fc: Layer already exists
0205cfc9b770: Layer already exists
adef16b9ec4f: Layer already exists
d690f8420aca: Layer already exists
274e3a2a827d: Layer already exists
7c255a74d815: Layer already exists
553c80416999: Layer already exists
107f7a71b278: Layer already exists
30320913a640: Layer already exists
d0c9d4f47624: Layer already exists
a49960e659f8: Layer already exists
52165657de87: Layer already exists
970398dbd0fa: Layer already exists
7b7f3078e1db: Layer already exists
9b55156abf26: Layer already exists
b626401ef603: Layer already exists
293d5db30c9f: Layer already exists
826c3ddbb29c: Layer already exists
03127cdb479b: Layer already exists
9c742cd6c7a5: Layer already exists
latest: digest: sha256:9c79c87eec9f3b90d23b6addae7711a51940a962533a2ae779719a86dfd1b23c size: 4935
> Task :sdks:java:container:java11:dockerTagsPush
> Task :sdks:python:container:py38:docker
---> Running in 14c7ea93e51a
Removing intermediate container 14c7ea93e51a
---> 2f716c2015bb
Step 4/32 : RUN apt-get update && apt-get install -y libsnappy-dev libyaml-dev ccache && rm -rf /var/lib/apt/lists/*
---> Running in 2ba58dec155d
Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 Packages [8184 kB]
Get:5 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [183 kB]
Get:6 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [2596 B]
Fetched 8578 kB in 2s (4162 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
libyaml-dev is already the newest version (0.2.2-1).
Suggested packages:
distcc | icecc
The following NEW packages will be installed:
ccache libsnappy-dev libsnappy1v5
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 495 kB of archives.
After this operation, 1425 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 ccache amd64 4.2-1 [446 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libsnappy1v5 amd64 1.1.8-1 [17.9 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 libsnappy-dev amd64 1.1.8-1 [31.1 kB]
[91mdebconf: delaying package configuration, since apt-utils is not installed
[0mFetched 495 kB in 0s (1792 kB/s)
Selecting previously unselected package ccache.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 23422 files and directories currently installed.)
Preparing to unpack .../ccache_4.2-1_amd64.deb ...
Unpacking ccache (4.2-1) ...
Selecting previously unselected package libsnappy1v5:amd64.
Preparing to unpack .../libsnappy1v5_1.1.8-1_amd64.deb ...
Unpacking libsnappy1v5:amd64 (1.1.8-1) ...
Selecting previously unselected package libsnappy-dev:amd64.
Preparing to unpack .../libsnappy-dev_1.1.8-1_amd64.deb ...
Unpacking libsnappy-dev:amd64 (1.1.8-1) ...
Setting up ccache (4.2-1) ...
Updating symlinks in /usr/lib/ccache ...
Setting up libsnappy1v5:amd64 (1.1.8-1) ...
Setting up libsnappy-dev:amd64 (1.1.8-1) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...
Removing intermediate container 2ba58dec155d
---> a17479785996
Step 5/32 : COPY target/base_image_requirements.txt /tmp/base_image_requirements.txt
---> aaa04d69a8b1
Step 6/32 : RUN pip install --no-deps -r /tmp/base_image_requirements.txt && python -c "import nltk; nltk.download('stopwords')" && rm /root/nltk_data/corpora/stopwords.zip && python -c "from google.protobuf.internal import api_implementation; assert api_implementation._default_implementation_type == 'cpp'; print ('Verified fast protobuf used.')" && rm -rf /root/.cache/pip && rm -rf /tmp/base_image_requirements.txt
---> Running in d8f4d0718e8f
> Task :sdks:java:container:java17:dockerPush9d9db56ca63b0f2dc5969d519000eb75dca223b3
2c73f40f1b07: Pushed
9d9db56ca63b0f2dc5969d519000eb75dca223b3: digest: sha256:60b888dc699e5ed136ad4cd2f8b1b51e43203a26d646b184eb3047aba0db5c3c size: 4729
> Task :sdks:java:container:java17:dockerTagLatest
> Task :sdks:python:container:py37:docker
Fetched 8578 kB in 2s (4460 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
libyaml-dev is already the newest version (0.2.2-1).
Suggested packages:
distcc | icecc
The following NEW packages will be installed:
ccache libsnappy-dev libsnappy1v5
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 495 kB of archives.
After this operation, 1425 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 ccache amd64 4.2-1 [446 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libsnappy1v5 amd64 1.1.8-1 [17.9 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 libsnappy-dev amd64 1.1.8-1 [31.1 kB]
[91mdebconf: delaying package configuration, since apt-utils is not installed
[0mFetched 495 kB in 0s (2683 kB/s)
Selecting previously unselected package ccache.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 23422 files and directories currently installed.)
Preparing to unpack .../ccache_4.2-1_amd64.deb ...
Unpacking ccache (4.2-1) ...
Selecting previously unselected package libsnappy1v5:amd64.
Preparing to unpack .../libsnappy1v5_1.1.8-1_amd64.deb ...
Unpacking libsnappy1v5:amd64 (1.1.8-1) ...
Selecting previously unselected package libsnappy-dev:amd64.
Preparing to unpack .../libsnappy-dev_1.1.8-1_amd64.deb ...
Unpacking libsnappy-dev:amd64 (1.1.8-1) ...
Setting up ccache (4.2-1) ...
Updating symlinks in /usr/lib/ccache ...
Setting up libsnappy1v5:amd64 (1.1.8-1) ...
Setting up libsnappy-dev:amd64 (1.1.8-1) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...
Removing intermediate container 2703cf4dc0a6
---> d4ab88cadced
Step 5/32 : COPY target/base_image_requirements.txt /tmp/base_image_requirements.txt
---> 5c08cd3ffbcc
Step 6/32 : RUN pip install --no-deps -r /tmp/base_image_requirements.txt && python -c "import nltk; nltk.download('stopwords')" && rm /root/nltk_data/corpora/stopwords.zip && python -c "from google.protobuf.internal import api_implementation; assert api_implementation._default_implementation_type == 'cpp'; print ('Verified fast protobuf used.')" && rm -rf /root/.cache/pip && rm -rf /tmp/base_image_requirements.txt
---> Running in 883abd788bd8
> Task :sdks:java:container:java17:dockerPushLatest
> Task :sdks:java:container:java17:dockerTagsPush
> Task :sdks:python:container:py39:docker
---> Running in a8e386b4b704
Removing intermediate container a8e386b4b704
---> 1be61a20f88d
Step 4/32 : RUN apt-get update && apt-get install -y libsnappy-dev libyaml-dev ccache && rm -rf /var/lib/apt/lists/*
---> Running in 26660a27b277
Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 Packages [8184 kB]
Get:5 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [183 kB]
Get:6 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [2596 B]
Fetched 8578 kB in 2s (4255 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
libyaml-dev is already the newest version (0.2.2-1).
Suggested packages:
distcc | icecc
The following NEW packages will be installed:
ccache libsnappy-dev libsnappy1v5
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 495 kB of archives.
After this operation, 1425 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 ccache amd64 4.2-1 [446 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libsnappy1v5 amd64 1.1.8-1 [17.9 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 libsnappy-dev amd64 1.1.8-1 [31.1 kB]
[91mdebconf: delaying package configuration, since apt-utils is not installed
[0mFetched 495 kB in 0s (1881 kB/s)
Selecting previously unselected package ccache.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 23422 files and directories currently installed.)
Preparing to unpack .../ccache_4.2-1_amd64.deb ...
Unpacking ccache (4.2-1) ...
Selecting previously unselected package libsnappy1v5:amd64.
Preparing to unpack .../libsnappy1v5_1.1.8-1_amd64.deb ...
Unpacking libsnappy1v5:amd64 (1.1.8-1) ...
Selecting previously unselected package libsnappy-dev:amd64.
Preparing to unpack .../libsnappy-dev_1.1.8-1_amd64.deb ...
Unpacking libsnappy-dev:amd64 (1.1.8-1) ...
Setting up ccache (4.2-1) ...
Updating symlinks in /usr/lib/ccache ...
Setting up libsnappy1v5:amd64 (1.1.8-1) ...
Setting up libsnappy-dev:amd64 (1.1.8-1) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...
Removing intermediate container 26660a27b277
---> 9fb9a131e082
Step 5/32 : COPY target/base_image_requirements.txt /tmp/base_image_requirements.txt
---> 0d00e8c5c59c
Step 6/32 : RUN pip install --no-deps -r /tmp/base_image_requirements.txt && python -c "import nltk; nltk.download('stopwords')" && rm /root/nltk_data/corpora/stopwords.zip && python -c "from google.protobuf.internal import api_implementation; assert api_implementation._default_implementation_type == 'cpp'; print ('Verified fast protobuf used.')" && rm -rf /root/.cache/pip && rm -rf /tmp/base_image_requirements.txt
---> Running in 08a69cec6b25
The command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
> Task :sdks:python:container:py39:docker FAILED
> Task :sdks:python:container:py38:docker FAILED
The command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
> Task :sdks:python:container:py37:docker FAILED
The command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
FAILURE: Build completed with 3 failures.
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py39:docker'.
> 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.
==============================================================================
2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py38:docker'.
> 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.
==============================================================================
3: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py37:docker'.
> 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
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 3 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
BUILD FAILED in 8m 44s
156 actionable tasks: 119 executed, 25 from cache, 12 up-to-date
Publishing build scan...
https://gradle.com/s/egx5fz7juwunc
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org
Build failed in Jenkins: beam_Publish_Beam_SDK_Snapshots #3889
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://ci-beam.apache.org/job/beam_Publish_Beam_SDK_Snapshots/3889/display/redirect>
Changes:
------------------------------------------
[...truncated 254.29 KB...]
> Task :sdks:python:container:py38:docker
Removing intermediate container e88be888961b
---> af0ff4e33bf5
Step 11/32 : RUN ln -s /usr/bin/ccache /usr/local/bin/gcc
---> Running in 17ed36e2ded6
Removing intermediate container 17ed36e2ded6
---> e2d4ea19a9b3
Step 12/32 : RUN ccache --set-config=sloppiness=file_macro && ccache --set-config=hash_dir=false
---> Running in aa293dc3ec8d
Removing intermediate container aa293dc3ec8d
---> e5331b8d5426
Step 13/32 : COPY target/apache-beam.tar.gz /opt/apache/beam/tars/
---> 10745b385f53
Step 14/32 : RUN pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]
---> Running in d34743c95946
Using pip 22.2.2 from /usr/local/lib/python3.8/site-packages/pip (python 3.8)
Processing /opt/apache/beam/tars/apache-beam.tar.gz
Preparing metadata (setup.py): started
[91m Running command python setup.py egg_info
[0m[91m Traceback (most recent call last):
[0m[91m File "<string>", line 2, in <module>
[0m[91m File "<pip-setuptools-caller>", line 34, in <module>
[0m[91m File "/tmp/pip-req-build-3fohrq8z/setup.py", line 169, in <module>
[0m[91m generate_protos_first()
[0m[91m File "/tmp/pip-req-build-3fohrq8z/setup.py", line 139, in generate_protos_first
[0m[91m gen_protos.generate_proto_files()
[0m[91m File "/tmp/pip-req-build-3fohrq8z/gen_protos.py", line 476, in generate_proto_files
[0m[91m raise RuntimeError(error_msg)
[0m[91m RuntimeError: Not in apache git tree, unable to find proto definitions.
[0m[91m error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
[0m[91m full command: /usr/local/bin/python -c '
exec(compile('"'"''"'"''"'"'
# This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
#
# - It imports setuptools before invoking setup.py, to enable projects that directly
# import from `distutils.core` to work with newer packaging standards.
# - It provides a clear error message when setuptools is not installed.
# - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
# setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
# manifest_maker: standard file '"'"'-c'"'"' not found".
# - It generates a shim setup.py, for handling setup.cfg-only projects.
import os, sys, tokenize
try:
import setuptools
except ImportError as error:
print(
"ERROR: Can not execute `setup.py` since setuptools is not available in "
"the build environment.",
file=sys.stderr,
)
sys.exit(1)
__file__ = %r
sys.argv[0] = __file__
if os.path.exists(__file__):
filename = __file__
with tokenize.open(__file__) as f:
setup_py_code = f.read()
else:
filename = "<auto-generated setuptools caller>"
setup_py_code = "from setuptools import setup; setup()"
exec(compile(setup_py_code, filename, "exec"))
'"'"''"'"''"'"' % ('"'"'/tmp/pip-req-build-3fohrq8z/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' egg_info --egg-base /tmp/pip-pip-egg-info-qi4xmwm1
[0m[91m cwd: /tmp/pip-req-build-3fohrq8z/
[0m Preparing metadata (setup.py): finished with status 'error'
[91merror: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
[0m
> Task :sdks:python:container:py39:docker FAILED
---> Running in cf8b3fba3bc3
Removing intermediate container cf8b3fba3bc3
---> 9daf5dbb6223
Step 12/32 : RUN ccache --set-config=sloppiness=file_macro && ccache --set-config=hash_dir=false
---> Running in 78463e959ca3
Removing intermediate container 78463e959ca3
---> e8b55ea6773e
Step 13/32 : COPY target/apache-beam.tar.gz /opt/apache/beam/tars/
---> 5101e80084cc
Step 14/32 : RUN pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]
---> Running in 4246aab997d9
Using pip 22.2.2 from /usr/local/lib/python3.9/site-packages/pip (python 3.9)
Processing /opt/apache/beam/tars/apache-beam.tar.gz
Preparing metadata (setup.py): started
[91m Running command python setup.py egg_info
[0m[91m Traceback (most recent call last):
[0m[91m File "<string>", line 2, in <module>
[0m[91m File "<pip-setuptools-caller>", line 34, in <module>
[0m[91m File "/tmp/pip-req-build-fq5q0tzt/setup.py", line 169, in <module>
[0m[91m generate_protos_first()
[0m[91m File "/tmp/pip-req-build-fq5q0tzt/setup.py", line 139, in generate_protos_first
[0m[91m gen_protos.generate_proto_files()
[0m[91m File "/tmp/pip-req-build-fq5q0tzt/gen_protos.py", line 476, in generate_proto_files
[0m[91m raise RuntimeError(error_msg)
[0m[91m RuntimeError: Not in apache git tree, unable to find proto definitions.
[0m[91m error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
[0m[91m full command: /usr/local/bin/python -c '
exec(compile('"'"''"'"''"'"'
# This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
#
# - It imports setuptools before invoking setup.py, to enable projects that directly
# import from `distutils.core` to work with newer packaging standards.
# - It provides a clear error message when setuptools is not installed.
# - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
# setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
# manifest_maker: standard file '"'"'-c'"'"' not found".
# - It generates a shim setup.py, for handling setup.cfg-only projects.
import os, sys, tokenize
try:
import setuptools
except ImportError as error:
print(
"ERROR: Can not execute `setup.py` since setuptools is not available in "
"the build environment.",
file=sys.stderr,
)
sys.exit(1)
__file__ = %r
sys.argv[0] = __file__
if os.path.exists(__file__):
filename = __file__
with tokenize.open(__file__) as f:
setup_py_code = f.read()
else:
filename = "<auto-generated setuptools caller>"
setup_py_code = "from setuptools import setup; setup()"
exec(compile(setup_py_code, filename, "exec"))
'"'"''"'"''"'"' % ('"'"'/tmp/pip-req-build-fq5q0tzt/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' egg_info --egg-base /tmp/pip-pip-egg-info-ps9ywfs7
[0m[91m cwd: /tmp/pip-req-build-fq5q0tzt/
[0m Preparing metadata (setup.py): finished with status 'error'
[91merror: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
[0mThe command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
> Task :sdks:python:container:py37:docker
---> Running in 1fc1e15c8c49
Removing intermediate container 1fc1e15c8c49
---> fa0e93ede71b
Step 12/32 : RUN ccache --set-config=sloppiness=file_macro && ccache --set-config=hash_dir=false
---> Running in fe84c359ea8e
Removing intermediate container fe84c359ea8e
---> 3f32fde70f47
Step 13/32 : COPY target/apache-beam.tar.gz /opt/apache/beam/tars/
---> fd4e3c8a1954
Step 14/32 : RUN pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]
---> Running in e3410e25d17a
Using pip 22.2.2 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)
Processing /opt/apache/beam/tars/apache-beam.tar.gz
Preparing metadata (setup.py): started
[91m Running command python setup.py egg_info
[0m[91m Traceback (most recent call last):
[0m[91m File "<string>", line 36, in <module>
[0m[91m File "<pip-setuptools-caller>", line 34, in <module>
[0m[91m File "/tmp/pip-req-build-kygga1va/setup.py", line 169, in <module>
[0m[91m generate_protos_first()
[0m[91m File "/tmp/pip-req-build-kygga1va/setup.py", line 139, in generate_protos_first
[0m[91m gen_protos.generate_proto_files()
[0m[91m File "/tmp/pip-req-build-kygga1va/gen_protos.py", line 476, in generate_proto_files
[0m[91m raise RuntimeError(error_msg)
[0m[91m RuntimeError: Not in apache git tree, unable to find proto definitions.
[0m
> Task :sdks:python:container:py38:docker FAILED
The command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
> Task :sdks:python:container:py37:docker FAILED
The command '/bin/sh -c pip install --no-deps -v /opt/apache/beam/tars/apache-beam.tar.gz[gcp]' returned a non-zero code: 1
FAILURE: Build completed with 3 failures.
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py39:docker'.
> 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.
==============================================================================
2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py38:docker'.
> 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.
==============================================================================
3: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:container:py37:docker'.
> 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
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 3 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
BUILD FAILED in 8m 49s
156 actionable tasks: 119 executed, 25 from cache, 12 up-to-date
Publishing build scan...
https://gradle.com/s/fkys3pbpr7exm
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscribe@beam.apache.org
For additional commands, e-mail: builds-help@beam.apache.org