See
<https://ci-beam.apache.org/job/beam_PreCommit_PythonDocker_Cron/3532/display/redirect?page=changes>
Changes:
[noreply] Publish results of JMH benchmark runs (Java SDK) to InfluxDB (part of
------------------------------------------
[...truncated 271.22 KB...]
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-28kqevgn/setup.py'"'"',),
"<pip-setuptools-caller>", "exec"))' egg_info --egg-base
/tmp/pip-pip-egg-info-dnst9tc7
[0m[91m cwd: /tmp/pip-req-build-28kqevgn/
[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:py38:docker FAILED
---> Running in 19abe938e0c2
Removing intermediate container 19abe938e0c2
---> 855dc554aede
Step 12/32 : RUN ccache --set-config=sloppiness=file_macro && ccache
--set-config=hash_dir=false
---> Running in c4d9616f2c07
Removing intermediate container c4d9616f2c07
---> 7465477ca5de
Step 13/32 : COPY target/apache-beam.tar.gz /opt/apache/beam/tars/
---> 6bb6b976e1a6
Step 14/32 : RUN pip install --no-deps -v
/opt/apache/beam/tars/apache-beam.tar.gz[gcp]
---> Running in 83cbc850ab4b
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-9t3uqj2z/setup.py", line 169, in <module>
[0m[91m generate_protos_first()
[0m[91m File "/tmp/pip-req-build-9t3uqj2z/setup.py", line 139, in
generate_protos_first
[0m[91m gen_protos.generate_proto_files()
[0m[91m File "/tmp/pip-req-build-9t3uqj2z/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-9t3uqj2z/setup.py'"'"',),
"<pip-setuptools-caller>", "exec"))' egg_info --egg-base
/tmp/pip-pip-egg-info-o__zvs6e
[0m[91m cwd: /tmp/pip-req-build-9t3uqj2z/
[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
:sdks:python:container:py38:docker (Thread[Execution worker Thread 7,5,main])
completed. Took 5 mins 38.672 secs.
> Task :sdks:python:container:py37:docker
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
:sdks:python:container:py37:docker (Thread[Execution worker Thread 5,5,main])
completed. Took 5 mins 38.728 secs.
> Task :sdks:python:container:py39:docker
Removing intermediate container 20046488586a
---> 3d8ab711b0e2
Step 11/32 : RUN ln -s /usr/bin/ccache /usr/local/bin/gcc
---> Running in 5e8aa4aa81d7
Removing intermediate container 5e8aa4aa81d7
---> 97767d070983
Step 12/32 : RUN ccache --set-config=sloppiness=file_macro && ccache
--set-config=hash_dir=false
---> Running in e0755d422061
Removing intermediate container e0755d422061
---> e938d101f76d
Step 13/32 : COPY target/apache-beam.tar.gz /opt/apache/beam/tars/
---> b30672c92774
Step 14/32 : RUN pip install --no-deps -v
/opt/apache/beam/tars/apache-beam.tar.gz[gcp]
---> Running in 6ac0d0fad1d0
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-polb36c6/setup.py", line 169, in <module>
[0m[91m generate_protos_first()
[0m[91m File "/tmp/pip-req-build-polb36c6/setup.py", line 139, in
generate_protos_first
[0m[91m gen_protos.generate_proto_files()
[0m[91m File "/tmp/pip-req-build-polb36c6/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-polb36c6/setup.py'"'"',),
"<pip-setuptools-caller>", "exec"))' egg_info --egg-base
/tmp/pip-pip-egg-info-y85cclgo
[0m[91m cwd: /tmp/pip-req-build-polb36c6/
[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:py39:docker FAILED
:sdks:python:container:py39:docker (Thread[Execution worker,5,main]) completed.
Took 5 mins 51.116 secs.
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 --debug option to get more log output.
==============================================================================
2: 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 --debug option to get more log output.
==============================================================================
3: 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 --debug option to get more log output.
==============================================================================
* Get more help at https://help.gradle.org
BUILD FAILED in 6m 29s
42 actionable tasks: 32 executed, 4 from cache, 6 up-to-date
Publishing build scan...
https://gradle.com/s/dhmj3qhidak4e
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]
