[
https://issues.apache.org/jira/browse/BEAM-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505871#comment-17505871
]
Beam JIRA Bot commented on BEAM-13373:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Python PostCommits produce too many spanner databases
> -----------------------------------------------------
>
> Key: BEAM-13373
> URL: https://issues.apache.org/jira/browse/BEAM-13373
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Brian Hulette
> Priority: P2
> Labels: stale-P2
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
