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_Admin failed #9366

Closed
flaky-bot bot opened this issue Feb 4, 2024 · 3 comments · Fixed by #9509 or #10476
Closed

bigtable: TestIntegration_Admin failed #9366

flaky-bot bot opened this issue Feb 4, 2024 · 3 comments · Fixed by #9509 or #10476
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 Feb 4, 2024

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


commit: 5bfee69
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 Feb 4, 2024
@product-auto-label product-auto-label bot added the api: bigtable Issues related to the Bigtable API. label Feb 4, 2024
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Feb 5, 2024
Copy link
Author

flaky-bot bot commented Feb 5, 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 (5bfee69), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@danieljbruce danieljbruce 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 Feb 5, 2024
@bhshkh
Copy link
Contributor

bhshkh commented Mar 5, 2024

Error:

=== RUN   TestIntegration_FullReadStats
    integration_test.go:3530: Running test against production
    integration_test.go:3569: Error creating column family: rpc error: code = FailedPrecondition desc = Could not modify schema of projects/dulcet-port-762/instances/gc-bt-it-instance/tables/cbt-test-1707036071564201376-11, due to concurrent modifications. This could mean another change to this tables schema, or a change to the replication topology (adding/removing a cluster).
    integration_test.go:1158: rpc error: code = FailedPrecondition desc = Could not modify schema of projects/dulcet-port-762/instances/gc-bt-it-instance/tables/cbt-test-1707036071564201376-11, due to concurrent modifications. This could mean another change to this tables schema, or a change to the replication topology (adding/removing a cluster).
--- FAIL: TestIntegration_FullReadStats (8.69s)


=== RUN   TestIntegration_Admin
    integration_test.go:1874: Number of Clusters with Encryption Info: 2, want: 1
    integration_test.go:3620: DeleteTable: retry failed with context deadline exceeded; last error: rpc error: code = DeadlineExceeded desc = context deadline exceeded
--- FAIL: TestIntegration_Admin (126.44s)

Copy link
Author

flaky-bot bot commented Mar 21, 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: b6574aa
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