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_NoUnicodeNormalization failed #3014

Closed
flaky-bot bot opened this issue Oct 14, 2020 · 11 comments · Fixed by #3027
Closed

storage: TestIntegration_NoUnicodeNormalization failed #3014

flaky-bot bot opened this issue Oct 14, 2020 · 11 comments · Fixed by #3027
Assignees
@tritone
Labels
api: storage Issues related to the Cloud Storage API. 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 Oct 14, 2020

This test failed!

To configure my behavior, see the Build Cop Bot documentation.

If I'm commenting on this issue too often, add the buildcop: quiet label and
I will stop commenting.

commit: 0113f76
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist
@flaky-bot flaky-bot bot added buildcop: issue 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 Oct 14, 2020
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label Oct 14, 2020
@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 14, 2020

commit: 77e9aad
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 14, 2020

commit: 1f708c9
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 14, 2020

commit: 6e22b50
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 14, 2020

commit: 93e8ec6
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 14, 2020

commit: 99bd00b
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 14, 2020

commit: 3c3a88d
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 14, 2020

commit: 213c13c
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

tritone added a commit to tritone/google-cloud-go that referenced this issue Oct 15, 2020
@tritone
test(storage): fix failing integration tests
f800c6d 
TestIntegration_ReadCRC and TestIntegration_NoUnicodeNormalization
depended on data in a bucket which has seemingly been deleted.
This rewrites them so that they create their own data instead.

Fixes googleapis#3016
Fixes googleapis#3014
@tritone tritone mentioned this issue Oct 15, 2020
Merged
@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 15, 2020

commit: 9e0153e
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 15, 2020

commit: 7f8e434
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

gcf-merge-on-green bot pushed a commit that referenced this issue Oct 15, 2020
@tritone
test(storage): fix failing integration tests (#3027)
b560988 
TestIntegration_ReadCRC and TestIntegration_NoUnicodeNormalization
depended on data in a bucket which has seemingly been deleted.
This rewrites them so that they create their own data instead.

Fixes #3016
Fixes #3014
@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 15, 2020

Looks like this issue is flaky. 😟

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

A human should fix and close this.

commit: ed991e3
buildURL: Build Status, Sponge
status: failed

Test output
integration_test.go:3525: integration_test.go:1891: read: storage: object doesn't exist

@flaky-bot flaky-bot bot reopened this Oct 15, 2020
@tritone
Copy link
Contributor

tritone commented Oct 16, 2020

This has indeed been fixed; build-cop-bot was confused by integration tests that were in the process of running when my fix was merged.

@tritone tritone closed this as completed Oct 16, 2020
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. 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
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test(storage): fix failing integration tests tritone/google-cloud-go
1 participant
@tritone