Repository navigation
add google-cloud-spanner to bulk-release once system tests pass #18341
Description
Activity
System tests are passing on the individual release #18340. Given that to be the case, the release isn't blocked so it is reasonable to downgrade this to a P2. However, we still need to fix the flaky tests and determine we should add this back to the bulk release.
The system test results do not display details of each test run. Merely which packages ran and the fact that the whole test timed out.
The packages that ran system tests in this session include these historically long-running sets of tests:- bigquery
- compute
- spanner
- bigtable
This is a case of the session timed out as opposed to there was a specific flaky test.
We need to continue working to decrease the turn-around time for system tests across the board.For the record, the spanner test in isolation takes ~31 minutes in toto(with setup/teardown)
- system-3.12(protobuf_implementation='python', database_dialect='GOOGLE_STANDARD_SQL'): 15 minutes
- system-3.12(protobuf_implementation='python', database_dialect='POSTGRESQL'): 11 minutes
Closing as OBE.
We are choosing to leave certain libraries out of bulk release to help control instances of CI timeouts and to grant product teams more flexibility over their own release schedule.
systems tests for google-cloud-spanner failed on a recent bulk release: #18293. As a result, it was moved to individual release: #18335.
See (build #7104): https://fusion2.corp.google.com/ci;prev=s/kokoro/prod:cloud-devrel%2Fclient-libraries%2Fpython%2Fgoogleapis%2Fgoogle-cloud-python%2Fpresubmit%2Fsystem/activity/042e3116-27da-4743-83c9-684ca8b11ce8/summary?q=google-cloud-python&s=p
Fix the system tests for google-cloud-spanner, and add it back to the bulk-release.