Skip to content
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

bigtable: TestIntegration_AdminBackup failed #10036

Open
flaky-bot bot opened this issue Apr 24, 2024 · 2 comments
Open

bigtable: TestIntegration_AdminBackup failed #10036

flaky-bot bot opened this issue Apr 24, 2024 · 2 comments
Assignees
Labels
api: bigtable Issues related to the 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
Copy link

flaky-bot bot commented Apr 24, 2024

Note: #9310 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.


commit: 9ff1733
buildURL: Build Status, Sponge
status: failed

@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Apr 24, 2024
@product-auto-label product-auto-label bot added the api: bigtable Issues related to the Bigtable API. label Apr 24, 2024
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Apr 24, 2024
Copy link
Author

flaky-bot bot commented Apr 24, 2024

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 (9ff1733), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@bhshkh bhshkh added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Apr 25, 2024
@bhshkh
Copy link
Contributor

bhshkh commented Apr 25, 2024

Reducing the priority of flaky tests to P2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigtable Issues related to the 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.
Projects
None yet
Development

No branches or pull requests

1 participant