Daniel Oliveira created BEAM-12249:
--------------------------------------
Summary: Python Postcommits timing out on postCommitIT
Key: BEAM-12249
URL: https://issues.apache.org/jira/browse/BEAM-12249
Project: Beam
Issue Type: Bug
Components: sdk-py-core, test-failures, testing
Reporter: Daniel Oliveira
Assignee: Benjamin Gonzalez
Test suites failing:
https://ci-beam.apache.org/job/beam_PostCommit_Python38/
https://ci-beam.apache.org/job/beam_PostCommit_Python37/
https://ci-beam.apache.org/job/beam_PostCommit_Python36/
They seem to be hanging on postCommitIT for some reason, with the following
logs repeating:
[Source|https://ci-beam.apache.org/job/beam_PostCommit_Python38/1146/console]
{noformat}
17:21:55 WARNING:root:Make sure that locally built Python SDK docker image has
Python 3.8 interpreter.
17:21:55 WARNING:apache_beam.runners.dataflow.dataflow_runner:Typical end users
should not use this worker jar feature. It can only be used when FnAPI is
enabled.
17:21:55 WARNING:apache_beam.options.pipeline_options:Discarding unparseable
args: ['--sleep_secs=20',
'--kms_key_name=projects/apache-beam-testing/locations/global/keyRings/beam-it/cryptoKeys/test']
17:22:03 WARNING:apache_beam.options.pipeline_options:Discarding unparseable
args: ['--sleep_secs=20',
'--kms_key_name=projects/apache-beam-testing/locations/global/keyRings/beam-it/cryptoKeys/test']
17:22:03 WARNING:root:Make sure that locally built Python SDK docker image has
Python 3.8 interpreter.
17:22:59 WARNING:apache_beam.runners.dataflow.dataflow_runner:Typical end users
should not use this worker jar feature. It can only be used when FnAPI is
enabled.
17:22:59 WARNING:apache_beam.options.pipeline_options:Discarding unparseable
args: ['--sleep_secs=20',
'--kms_key_name=projects/apache-beam-testing/locations/global/keyRings/beam-it/cryptoKeys/test']
17:23:08 WARNING:apache_beam.options.pipeline_options:Discarding unparseable
args: ['--sleep_secs=20',
'--kms_key_name=projects/apache-beam-testing/locations/global/keyRings/beam-it/cryptoKeys/test']
{noformat}
The root cause seems to be PR #14481.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
