You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 8, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 8, 2026. It is now read-only.
samples.samples.snippets_test: many tests failed #437
Many tests failed at the same time in this package.
I will close this issue when there are no more failures in this package and
there is at least one pass.
No new issues will be filed for this package until this issue is closed.
If there are already issues for individual test cases, I will close them when
the corresponding test passes. You can close them earlier, if you prefer, and
I won't reopen them while this issue is still open.
At least some of the failures I'm seeing are due to timeouts in instance creation, exceeding 120 seconds. Do we have some way to ask the back-end folks if they have had recent lags in provisioning instances?
The multiple snippets failures may be due to insufficient dependencies (or I implemented the pytest-dependency bits wrong). They do all seem to be either timeouts (for instance creation) or NotFound errors for the instance / database being used.
Activity
larkee commentedon Jul 29, 2021
@tseaver All of the samples and system tests are suddenly timing out. Looks related to: #427
Is this an issue in other libraries? I need to do a release so I'd like to either resolve the issue or revert that change. WDYT?
tseaver commentedon Jul 29, 2021
I know that we have reverted / disable
always_use_jwt_accessPRs in other libraries (googleapis/python-bigquery#722, googleapis/python-bigtable#348), in some cases followed by a different enabling PR (googleapis/python-bigtable#397). That latter PR, however, looks a lot like our #427. :(tseaver commentedon Jul 29, 2021
At least some of the failures I'm seeing are due to timeouts in instance creation, exceeding 120 seconds. Do we have some way to ask the back-end folks if they have had recent lags in provisioning instances?
tseaver commentedon Jul 29, 2021
The multiple
snippetsfailures may be due to insufficient dependencies (or I implemented thepytest-dependencybits wrong). They do all seem to be either timeouts (for instance creation) or NotFound errors for the instance / database being used.tests: harden old instance cleanup against NotFound
tests: harden old instance cleanup against NotFound (#471)
flaky-bot commentedon Jul 30, 2021
Test passed for commit 89fe076 (Build Status, Sponge)! Closing this issue.