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_PostPolicyV4 failed #6212

Closed
flaky-bot bot opened this issue Jun 17, 2022 · 1 comment · Fixed by #6271
Closed

storage: TestIntegration_PostPolicyV4 failed #6212

flaky-bot bot opened this issue Jun 17, 2022 · 1 comment · Fixed by #6271
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: 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 Jun 17, 2022

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: a2cdd05
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:4320: Post "https://storage.googleapis.com/go-integration-test-20220617-64589178484107-0047/": read tcp 10.142.0.167:43298->172.217.193.128:443: read: connection reset by peer
    integration_test.go:4735: panic.go:636: delete object go-integration-test-20220617-64589178484107-0048 from bucket go-integration-test-20220617-64589178484107-0047: storage: object doesn't exist
@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 Jun 17, 2022
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label Jun 17, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented Jun 17, 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 (a2cdd05), 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 Jun 17, 2022
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Jun 22, 2022
@BenWhitehead BenWhitehead 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. 🚨 This issue needs some love. labels Jun 24, 2022
tritone added a commit to tritone/google-cloud-go that referenced this issue Jun 29, 2022
This test verifies that the upload works using a basic net/http
client, so we need to account for the fact that that client doesn't
include retries.

Fixes googleapis#6212
tritone added a commit that referenced this issue Jun 30, 2022
This test verifies that the upload works using a basic net/http
client, so we need to account for the fact that that client doesn't
include retries.

Fixes #6212
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: 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
Development

Successfully merging a pull request may close this issue.

3 participants