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

storage: TestIntegration_ACL failed #6379

Closed
flaky-bot bot opened this issue Jul 20, 2022 · 1 comment · Fixed by #6392
Closed

storage: TestIntegration_ACL failed #6379

flaky-bot bot opened this issue Jul 20, 2022 · 1 comment · Fixed by #6392
Assignees
Labels
api: storage Issues related to the Cloud Storage 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: 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.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Jul 20, 2022

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


commit: 0c563c8
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:2365: Write for acl2 failed with googleapi: Error 429: The rate of change requests to the object go-integration-test-20220720-29426005696819-0001/acl2 exceeds the rate limit. Please reduce the rate of create, update, and delete requests., rateLimitExceeded
    integration_test.go:2365: Write for acl2 failed with googleapi: Error 429: The rate of change requests to the object go-integration-test-20220720-29426005696819-0001/acl2 exceeds the rate limit. Please reduce the rate of create, update, and delete requests., rateLimitExceeded
    integration_test.go:2365: Write for acl2 failed with googleapi: Error 429: The rate of change requests to the object go-integration-test-20220720-29426005696819-0001/acl2 exceeds the rate limit. Please reduce the rate of create, update, and delete requests., rateLimitExceeded
    integration_test.go:2365: Write for acl2 failed with googleapi: Error 429: The rate of change requests to the object go-integration-test-20220720-29426005696819-0001/acl2 exceeds the rate limit. Please reduce the rate of create, update, and delete requests., rateLimitExceeded
    integration_test.go:2383: object ACL: could not delete entity domain-google.com
@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 Jul 20, 2022
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label Jul 20, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented Jul 20, 2022

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

@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Jul 20, 2022
tritone added a commit to tritone/google-cloud-go that referenced this issue Jul 21, 2022
Few minor changes to make sure potentially flaky and/or
eventually consistent operations for ACLs are retried appropriately.

Fixes googleapis#6379
tritone added a commit that referenced this issue Jul 21, 2022
Few minor changes to make sure potentially flaky and/or
eventually consistent operations for ACLs are retried appropriately.

Fixes #6379
noahdietz added a commit that referenced this issue Jul 21, 2022
* chore: release main (#6351)

* test(profiler): compile busybench before running backoff test (#6375)

* chore(bigquery/storage/managedwriter): augment test logging (#6373)

* chore(storage): RewriteObject implementation (#6313)

* chore(storage): RewriteObject implementation

* address feedback

* refactor source/destination object types

* address feedback

* address feedback

* fix test

* chore(main): release storage 1.24.0 (#6336)

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Chris Cotter <cjcotter@google.com>

* chore(internal/gapicgen): update microgen v0.31.2 (#6383)

Only includes fixes to regapic generation.

* test(bigquery/storage/managedwriter): relax error checking (#6385)

When a user issues a large request, the response from the
backend is a bare "InvalidArgument".  This PR removes additional
validation on information that is only attached when interrogating
the backend from a known client; it's stripped in the normal case.

Internal issue 239740070 was created to address the unactionable
nature of the response.

Fixes: #6361

* feat(firestore): adds Bulkwriter support to Firestore client (#5946)

* feat: adds Bulkwriter support to Firestore client

* test(storage): unflake TestIntegration_ACL (#6392)

Few minor changes to make sure potentially flaky and/or
eventually consistent operations for ACLs are retried appropriately.

Fixes #6379

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Amarin (Um) Phaosawasdi <amchiclet@users.noreply.github.com>
Co-authored-by: shollyman <shollyman@google.com>
Co-authored-by: Noah Dietz <noahdietz@users.noreply.github.com>
Co-authored-by: Chris Cotter <cjcotter@google.com>
Co-authored-by: Eric Schmidt <erschmid@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: storage Issues related to the Cloud Storage 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: 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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant