[Failing Test]: Python PostCommit failing from apache_beam.io.external.xlang_jdbcio_it_test.CrossLanguageJdbcIOTest

[damondouglas]

What happened?

Situation

https://github.com/apache/beam/actions/workflows/beam_PostCommit_Python.yml shows consistent failure starting at https://github.com/apache/beam/actions/runs/12150002715 due to failures:

apache_beam.io.external.xlang_jdbcio_it_test.CrossLanguageJdbcIOTest: test_xlang_jdbc_write_read_0_postgres

and

apache_beam.io.external.xlang_jdbcio_it_test.CrossLanguageJdbcIOTest: test_xlang_jdbc_write_read_1_mysql

Background

Failures began after commit, https://github.com/apache/beam/tree/2fe725d92a0311677b3e6f5ffcd3838064ca2932. Commits immediately after said commit that existed at the first failure were:

• jdbcio write batch config changes (jdbcio write batch config changes #33205)
• Tour of Beam: formatting/typos (Tour of Beam: formatting/typos #33249)
• [yaml] error_handling normalization follow-up

Further inspection of the failing Gradle tasks reveals:
:sdks:python:test-suites:portable:py39:postCommitPy39IT

Assessment

#33205 is the most likely root cause as it contains related code changes under test via CrossLanguageJdbcIOTest.

Recommendation

Investigate related code in #33205 to rule in any specific breaking changes.

Issue Failure

Failure: Test is flaky

Issue Priority

Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner