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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot logged work on BEAM-13373:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Dec/21 22:41
            Start Date: 02/Dec/21 22:41
    Worklog Time Spent: 10m 
      Work Description: y1chi commented on pull request #16112:
URL: https://github.com/apache/beam/pull/16112#issuecomment-985060446


   Realized that they are also running in dataflow suite and portable runner suite, will add more changes to those as well


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 689646)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>          Time Spent: 10m
>  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)