Build failed in Jenkins: beam_PostCommit_Python39 #849

[Apache Jenkins Server]

See 
<https://ci-beam.apache.org/job/beam_PostCommit_Python39/849/display/redirect?page=changes>

Changes:

[noreply] Add streaming test for Write API sink (#21903)

[noreply] [Go SDK] Proto changes for timer param (#23216)

[noreply] Bump github.com/testcontainers/testcontainers-go in /sdks (#23201)

[noreply] Update to objsize to 0.5.2 which is under BSD-3 license (fixes #23096)

[noreply] Exclude insignificant whitespace from cloud object (#23217)

[noreply] Trying out property-based tests for Beam python coders (#22233)


------------------------------------------
[...truncated 151.06 KB...]

┌─────────────────────────────────────────────────────────────────────────────┐
│                     These components will be installed.              
       │
├─────────────────────────────────────────────────────┬────────────┬──────────┤
│                         Name                        │  Version   │   
Size   │
├─────────────────────────────────────────────────────┼────────────┼──────────┤
│ BigQuery Command Line Tool                         
 │     2.0.75 │  1.6 MiB 
│
│ BigQuery Command Line Tool (Platform Specific)     
 │     2.0.75 │  < 1 
MiB │
│ Cloud Storage Command Line Tool                    
 │       5.13 │ 15.5 
MiB │
│ Cloud Storage Command Line Tool (Platform Specific) 
│       5.11 │  < 1 MiB 
│
│ Google Cloud CLI Core Libraries (Platform 
Specific) │ 2022.08.05 │  < 1 
MiB │
│ Google Cloud CRC32C Hash Tool                       │ 
     1.0.0 │  1.2 MiB │
│ anthoscli                                          
 │     0.2.29 │ 37.6 
MiB │
│ gcloud cli dependencies                             │ 
2021.04.16 │  < 1 MiB 
│
└─────────────────────────────────────────────────────┴────────────┴──────────┘

For the latest full release notes, please visit:
  https://cloud.google.com/sdk/release_notes

╔════════════════════════════════════════════════════════════╗
╠═ Creating update staging area                             ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: BigQuery Command Line Tool                   ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: BigQuery Command Line Tool (Platform Spec... ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: Cloud Storage Command Line Tool              ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: Cloud Storage Command Line Tool (Platform... ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: Default set of gcloud commands               ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: Google Cloud CLI Core Libraries (Platform... ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: Google Cloud CRC32C Hash Tool                ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: Google Cloud CRC32C Hash Tool                ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: anthoscli                                    ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: anthoscli                                    ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Installing: gcloud cli dependencies                      ═╣
╚════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════╗
╠═ Creating backup and activating new installation          ═╣
╚════════════════════════════════════════════════════════════╝

Performing post processing steps...
........................................................................................................done.

Update done!


To help improve the quality of this product, we collect anonymized usage data
and anonymized stacktraces when crashes are encountered; additional information
is available at <https://cloud.google.com/sdk/usage-statistics>. This data is
handled in accordance with our privacy policy
<https://cloud.google.com/terms/cloud-privacy-notice>. You may choose to opt in 
this
collection now (by choosing 'Y' at the below prompt), or at any time in the
future by running the following command:

    gcloud config set disable_usage_reporting false


This will install all the core command line tools necessary for working with
the Google Cloud Platform.

==> Source [/usr/local/gcloud/google-cloud-sdk/completion.bash.inc] in 
your profile to enable shell command completion for gcloud.
==> Source [/usr/local/gcloud/google-cloud-sdk/path.bash.inc] in your profile 
to add the Google Cloud SDK command line tools to your $PATH.

For more information on how to get started, please visit:
  https://cloud.google.com/sdk/docs/quickstarts


Removing intermediate container 5b638f7acfde
 ---> dedf24c5f716
Step 11/32 : RUN ln -s /usr/bin/ccache /usr/local/bin/gcc
 ---> Running in f93d21fed14d
Removing intermediate container f93d21fed14d
 ---> e6c97e2bc47f
Step 12/32 : RUN ccache --set-config=sloppiness=file_macro && ccache 
--set-config=hash_dir=false
 ---> Running in 9e4dbef57089
Removing intermediate container 9e4dbef57089
 ---> d0a93ce4d52d
Step 13/32 : COPY target/apache-beam.tar.gz /opt/apache/beam/tars/
 ---> 251ffc436351
Step 14/32 : RUN pip install --no-deps -v 
/opt/apache/beam/tars/apache-beam.tar.gz[gcp]
 ---> Running in d481eacff47f
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-ilyj3j2x/setup.py", line 169, in <module>
      generate_protos_first()
    File "/tmp/pip-req-build-ilyj3j2x/setup.py", line 139, in 
generate_protos_first
      gen_protos.generate_proto_files()
    File "/tmp/pip-req-build-ilyj3j2x/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-ilyj3j2x/setup.py'"'"',), 
"<pip-setuptools-caller>", "exec"))' egg_info --egg-base 
/tmp/pip-pip-egg-info-06pgafy_
  cwd: /tmp/pip-req-build-ilyj3j2x/
  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:py39:docker FAILED

FAILURE: Build completed with 5 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task 
':sdks:python:test-suites:dataflow:py39:installGcpTest'.
> Process 'command 'sh'' 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:test-suites:portable:py39:installGcpTest'.
> Process 'command 'sh'' 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.
-----------
* Where:
Script 
'<https://ci-beam.apache.org/job/beam_PostCommit_Python39/ws/src/sdks/python/test-suites/direct/common.gradle'>
 line: 182

* What went wrong:
Execution failed for task 
':sdks:python:test-suites:direct:py39:hdfsIntegrationTest'.
> Process 'command 'sh'' 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.
==============================================================================

4: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':sdks:python:test-suites:direct:py39:installGcpTest'.
> Process 'command 'sh'' 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.
==============================================================================

5: 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.
==============================================================================

* 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 1 invalid unit(s) of work during 
this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD FAILED in 5m 1s
214 actionable tasks: 145 executed, 63 from cache, 6 up-to-date

Publishing build scan...
https://gradle.com/s/dit3rtey3f3ce

Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure

---------------------------------------------------------------------
To unsubscribe, e-mail: builds-unsubscr...@beam.apache.org
For additional commands, e-mail: builds-h...@beam.apache.org