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
  cwd: /tmp/pip-req-build-mqaspog5/
  Preparing metadata (setup.py): finished with status 'error'
error: 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.
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: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
  Running command python setup.py egg_info
  Traceback (most recent call last):
    File "<string>", line 36, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-req-build-6ieu_ha_/setup.py", line 169, in <module>
      generate_protos_first()
    File "/tmp/pip-req-build-6ieu_ha_/setup.py", line 139, in 
generate_protos_first
      gen_protos.generate_proto_files()
    File "/tmp/pip-req-build-6ieu_ha_/gen_protos.py", line 476, in 
generate_proto_files
      raise RuntimeError(error_msg)
  RuntimeError: Not in apache git tree, unable to find proto 
definitions.
  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.
  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
  cwd: /tmp/pip-req-build-6ieu_ha_/
  Preparing metadata (setup.py): finished with status 'error'
error: 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.

> 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
  Running command python setup.py egg_info
  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-req-build-kj1nl1eu/setup.py", line 169, in <module>
      generate_protos_first()
    File "/tmp/pip-req-build-kj1nl1eu/setup.py", line 139, in 
generate_protos_first
      gen_protos.generate_proto_files()
    File "/tmp/pip-req-build-kj1nl1eu/gen_protos.py", line 476, in 
generate_proto_files
      raise RuntimeError(error_msg)
  RuntimeError: Not in apache git tree, unable to find proto 
definitions.
  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.
  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
  cwd: /tmp/pip-req-build-kj1nl1eu/
  Preparing metadata (setup.py): finished with status 'error'
error: 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.
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: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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to