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.

Sign up for GitHub

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

Jump to bottom

storage: TestIntegration_BucketCreateDelete failed #10178

Closed
flaky-bot bot opened this issue May 15, 2024 · 7 comments
Closed

storage: TestIntegration_BucketCreateDelete failed #10178

flaky-bot bot opened this issue May 15, 2024 · 7 comments
Assignees
@tritone
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: 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 May 15, 2024

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: 292e812
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 May 15, 2024
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label May 15, 2024
@tritone
Copy link
Contributor

tritone commented May 15, 2024

Looks like this failed due to a timeout/panic for gRPC:

=== RUN TestIntegration_BucketCreateDelete/grpc/no_attrs panic: test timed out after 45m0s

We should figure out how to set a shorter timeout here that doesn't cause the whole run to panic.

@tritone tritone 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 May 15, 2024
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented May 15, 2024

Test passed for commit 8e675cd (Build Status, Sponge)! Closing this issue.

@flaky-bot flaky-bot bot closed this as completed May 15, 2024
@flaky-bot flaky-bot bot reopened this May 15, 2024
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label May 15, 2024
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented May 15, 2024

Looks like this issue is flaky. 😟

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

A human should fix and close this.

commit: 75e8fd0
buildURL: Build Status, Sponge
status: failed

tritone added a commit to tritone/google-cloud-go that referenced this issue May 17, 2024
@tritone
test(storage): add timeout for bucket create test
e6b157f 
This test has flaked a few times lately after running for
the full duration of the integration test run timeout, causing
a panic. Add a shorter timeout to help debug future flakes.

Updates googleapis#10178
@tritone tritone mentioned this issue May 17, 2024
Merged
BrennaEpp pushed a commit that referenced this issue May 17, 2024
@tritone
test(storage): add timeout for bucket create test (#10216)
4dd2f4d 
This test has flaked a few times lately after running for
the full duration of the integration test run timeout, causing
a panic. Add a shorter timeout to help debug future flakes.

Updates #10178
@tritone
Copy link
Contributor

tritone commented May 17, 2024

After adding the timeout we get:

integration_test.go:452: bucket create: retry failed with context deadline exceeded; last error: rpc error: code = Unavailable desc = We encountered an internal error. Please try again.

@tritone
Copy link
Contributor

tritone commented May 17, 2024

This seems to be a service issue, closing now.

@tritone tritone closed this as completed May 17, 2024
tritone added a commit to tritone/google-cloud-go that referenced this issue May 18, 2024
@tritone
test(storage): add 5m timeout per integration test
8a75019 
This allows easier debugging when integration test runs get
stalled as in googleapis#10178
@tritone tritone mentioned this issue May 18, 2024
Merged
tritone added a commit that referenced this issue May 18, 2024
@tritone
test(storage): add 5m timeout per integration test (#10227)
e2cf46b 
This allows easier debugging when integration test runs get
stalled as in #10178
@flaky-bot flaky-bot bot reopened this May 20, 2024
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented May 20, 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: cb965ed
buildURL: Build Status, Sponge
status: failed

@tritone tritone closed this as completed May 20, 2024
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented May 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: a495f8f
buildURL: Build Status, Sponge
status: failed

@flaky-bot flaky-bot bot reopened this May 21, 2024
@flaky-bot flaky-bot bot mentioned this issue May 23, 2024
Closed
@tritone tritone closed this as completed May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tritone tritone

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: 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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tritone