[BEAM-13373] Python PostCommits produce too many spanner databases

• Type: Bug
• Status: Open
• Priority: P3
• Resolution: Unresolved
• Component/s: testing
• Assignee: Unassigned
• Reporter: Brian Hulette
• Created: 02/Dec/21 22:12
• Updated: 04/Jun/22 21:49

Description

There are ~30 Python PostCommit tests that create and destroy a Spanner Database. Each running across 3 PostCommits. We should reduce the number of tests that do this.

A couple of avenues:
1. Only run Spanner ITs in one Python version's PostCommit.
2. Verify more logic in spannerio_test.py (as opposed to spannerio_*_it_test.py), which uses a mock rather than prod Spanner. We can still have a few ITs, but we don't need to verify everything there.

Issue Links

• is cloned by: BEAM-13375 Java PostCommits produce too many spanner databases
• relates to: BEAM-13337 Leaking Databases in Spanner instance apache-beam-testing:beam-test
• links to: GitHub Pull Request #16112
• links to: GitHub Pull Request #16141