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_ConditionalMutations failed #11505

Open
flaky-bot bot opened this issue Jan 24, 2025 · 2 comments
Open

bigtable: TestIntegration_ConditionalMutations failed #11505

flaky-bot bot opened this issue Jan 24, 2025 · 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: p3 Desirable enhancement or 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 24, 2025

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


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

flaky-bot bot commented Jan 24, 2025

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

@bhshkh bhshkh added priority: p3 Desirable enhancement or 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 25, 2025
@bhshkh
Copy link
Contributor

bhshkh commented Jan 25, 2025

Error from logs:

=== RUN   TestIntegration_ConditionalMutations
    integration_test.go:4417: Running test against production
    retry.go:49: Fatal failure after 2 attempts:
        integration_test.go:4553: rpc error: code = AlreadyExists desc = Cannot create existing family follows
        retry.go:112: rpc error: code = AlreadyExists desc = Cannot create existing family follows
    integration_test.go:187: Mutating row "j§adams": rpc error: code = NotFound desc = Error while mutating the row 'j\302\247adams' (projects/dulcet-port-762/instances/gc-bt-it-instance/tables/cbt-test-1737739226383752817-01) : Requested column family not found.
--- FAIL: TestIntegration_ConditionalMutations (103.23s)

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: p3 Desirable enhancement or 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