| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This pull request reorganizes imports and increases the retry deadline from 0.1 to 1.0 seconds in the unit tests test_async_job_retry.py and test_query_job_retry.py for Google Cloud BigQuery jobs. There are no review comments, so I have no feedback to provide.
Sorry, something went wrong.
> [!note] > - This is intended to test parallelization of system tests in CI/CD. > - It is paired with a non-parallelized version to benchmark any improvement. #17645 ### Results Baseline: [2 hours 5 mins](https://btx.cloud.google.com/invocations/34ed19da-da1a-4cae-bc1b-a1f52ca20927/targets) With parallelization: [42 mins](https://btx.cloud.google.com/invocations/c0b4abe6-806b-4818-87b0-6b1574c075e7/targets) This was blocked on: #17826
| Back | FazBrowse Home | New Git URL |
The Problem
Two unit tests in google-cloud-bigquery (test_result_w_retry_wo_state and test_result_w_custom_retry) were failing intermittently with a TimeoutError or RetryError. This flakiness occurs because the tests use a very short inner retry deadline of 0.1 seconds. Under heavy load (such as during parallel testing or on constrained continuous integration runners), this deadline can be exceeded, causing the test to fail confusingly.
The Solution
Increased the deadline parameter for the custom retry objects in both tests from 0.1 seconds to 1.0 seconds. This provides enough buffer for the test assertions to complete without timing out, aligning with other similar tests in the suite.
Notes to Reviewers
Here is a snippet of the failure: