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_MultiChunkWrite failed #7033

Closed
flaky-bot bot opened this issue Nov 12, 2022 · 2 comments · Fixed by #7193
Closed

storage: TestIntegration_MultiChunkWrite failed #7033

flaky-bot bot opened this issue Nov 12, 2022 · 2 comments · Fixed by #7193
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 Nov 12, 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: feb6b0a
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:1099: TestIntegration_MultiChunkWrite/grpc: committed 1048576
    integration_test.go:1103: Writer.Write: rpc error: code = InvalidArgument desc = Field `object_checksums` is only allowed on StartResumableWriteRequest, WriteObjectRequest with write_offset=0 or WriteObjectRequest with finish_write=true.
    integration_test.go:4792: panic.go:540: delete object go-integration-test-1668209526808651231-19 from bucket golang-grpc-test-1668209526808651231-01: 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 Nov 12, 2022
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label Nov 12, 2022
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Nov 12, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented Nov 12, 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 (feb6b0a), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@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 Nov 16, 2022
@codyoss
Copy link
Member

codyoss commented Dec 27, 2022

This is causing nightly to fail consistently will be skipping the test for now.

codyoss added a commit to codyoss/google-cloud-go that referenced this issue Dec 27, 2022
gcf-merge-on-green bot pushed a commit that referenced this issue Dec 27, 2022
The gRPC variant of this test always fails.

Updates: #7033
gcf-merge-on-green bot pushed a commit that referenced this issue Dec 27, 2022
There was an API change so that checksums can now only be provided by the StartResumableUpload request rather than while uploading. Send the checksum at this stage instead.

Fixes #7033
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.

2 participants