bigtable: TestIntegration_FullReadStats failed

[flaky-bot[bot]]

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and I will stop commenting.

---

commit: 5bfee69e5e6b46c99fb04df2c7f6de560abe0655 buildURL: Build Status, Sponge status: failed

[flaky-bot[bot]]

Looks like this issue is flaky. :worried:

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (5bfee69e5e6b46c99fb04df2c7f6de560abe0655), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[bhshkh]

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)

[flaky-bot[bot]]

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

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

---

commit: b6574aa42ebad0532c2749b6ece879b932f95cb9 buildURL: Build Status, Sponge status: failed