[go: nahoru, domu]

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_AdminCopyBackup failed #9258

Open
flaky-bot bot opened this issue Jan 12, 2024 · 4 comments · Fixed by #9270 or #9509
Open

bigtable: TestIntegration_AdminCopyBackup failed #9258

flaky-bot bot opened this issue Jan 12, 2024 · 4 comments · Fixed by #9270 or #9509
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 Jan 12, 2024

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


commit: 4a132f9
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 Jan 12, 2024
@product-auto-label product-auto-label bot added the api: bigtable Issues related to the Bigtable API. label Jan 12, 2024
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Jan 13, 2024
Copy link
Author
flaky-bot bot commented Jan 13, 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 (4a132f9), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@bhshkh bhshkh linked a pull request Jan 17, 2024 that will close this issue
@daniel-sanche daniel-sanche 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 Jan 17, 2024
@flaky-bot flaky-bot bot reopened this Jan 23, 2024
Copy link
Author
flaky-bot bot commented Jan 23, 2024

Oops! Looks like this issue is still flaky. It failed again. 😬

I reopened the issue, but a human will need to close it again.


commit: 3213b45
buildURL: Build Status, Sponge
status: failed

@bhshkh
Copy link
Contributor
bhshkh commented Mar 5, 2024

Error from build log:

=== RUN   TestIntegration_AdminCopyBackup
    integration_test.go:3114: CreateCluster: rpc error: code = FailedPrecondition desc = Cannot create multiple clusters in the same zone.
    retry.go:44: FAILED after 3 attempts:
        integration_test.go:3101: DeleteCluster: rpc error: code = NotFound desc = Cluster projects/dulcet-port-762/instances/gc-bt-it-instance/clusters/bt-c--1706053464118262834-03 does not exist.
--- FAIL: TestIntegration_AdminCopyBackup (13.24s)

Copy link
Author
flaky-bot bot commented Mar 15, 2024

Oops! Looks like this issue is still flaky. It failed again. 😬

I reopened the issue, but a human will need to close it again.


commit: 93c7bc0
buildURL: Build Status, Sponge
status: failed

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
2 participants