[jira] [Commented] (BEAM-13373) Python PostCommits produce too many spanner databases

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472878#comment-17472878 ] 

Beam JIRA Bot commented on BEAM-13373:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> 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
>            Assignee: Yichi Zhang
>            Priority: P2
>              Labels: stale-assigned
>          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)