[
https://issues.apache.org/jira/browse/BEAM-13373?focusedWorklogId=691445&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-691445
]
ASF GitHub Bot logged work on BEAM-13373:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Dec/21 02:22
Start Date: 07/Dec/21 02:22
Worklog Time Spent: 10m
Work Description: y1chi commented on pull request #16141:
URL: https://github.com/apache/beam/pull/16141#issuecomment-987507655
> > Why should we prefer to run these tests in 3.6 instead of 3.7? I don't
see how this would help alleviate the issue.
Good point, I was thinking that python 3.7 was already running all other
integration tests such as hdfsIT and now it is timing out because it has to run
spanner io it. But look again at python post commit for other versions, the
post commit itself is already taking close to 2 hour time limit.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 691445)
Time Spent: 3h (was: 2h 50m)
> 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: 3h
> 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)
