-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BigQuery: 'test_extract_table' snippet, bucket creation flakes with 500 #5886
Comments
The
And a new, unguarded one for |
Possibly related to https://status.cloud.google.com/incident/storage/18003 |
@shollyman Thanks for linking the incident: that is a likely culprit. |
@tswast, @shollyman Should we just decide to write off those GCS failures as "sunspots"? Or do you think we need to harden our tests against 500 / 503 response codes from GCS (in addition to the 429 we already retry for)? |
Ugh, just happened again. |
We could change the bucket to regional instead of multi-regional? We could also put the bucket creation / destruction into a module-level test fixture to avoid doing as many calls to GCS. |
Similar to #5746, #5747, #5748, but with a 500 error instead of a 429.
See: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/7904 (first error in
snippets-2-7
run).The text was updated successfully, but these errors were encountered: