Bigtable backups: should restore a backup to a different instance failed #1465
Labels
api: bigtable
Issues related to the googleapis/nodejs-bigtable API.
flakybot: flaky
Tells the Flaky Bot not to close or comment on this issue.
flakybot: issue
An issue filed by the Flaky Bot. Should not be added manually.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Comments
flaky-bot
bot
added
flakybot: issue
product-auto-label
bot
added
the
api: bigtable
flaky-bot
bot
added
the
flakybot: flaky
|
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. When run at the same commit (ed942c5), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: #1202 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: ed942c5
buildURL: Build Status, Sponge
status: failed
The text was updated successfully, but these errors were encountered: