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

spanner: TestIntegration_BatchQuery failed #1922

Closed
flaky-bot bot opened this issue Apr 15, 2020 · 15 comments
Closed

spanner: TestIntegration_BatchQuery failed #1922

flaky-bot bot opened this issue Apr 15, 2020 · 15 comments
Assignees
Labels
api: spanner Issues related to the Spanner API. 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 Apr 15, 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: 891bf76
buildURL: Build Status, Sponge
status: failed

@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 Apr 15, 2020
@flaky-bot
Copy link
Author

flaky-bot bot commented Apr 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: 891bf76
buildURL: Build Status, Sponge
status: passed

@tbpg tbpg added the api: spanner Issues related to the Spanner API. label Apr 15, 2020
@olavloite
Copy link
Contributor

@skuruppu These flaky failures are caused by UNAVAILABLE errors on CreateDatabase RPCs.

@skuruppu
Copy link
Contributor

@olavloite, oh I see. Does that mean we could do a similar thing to what you proposed for Java where we add a retry loop for non-idempotent RPCs?

@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Apr 22, 2020
@skuruppu skuruppu assigned olavloite and unassigned skuruppu Apr 23, 2020
@skuruppu
Copy link
Contributor

@olavloite if you can implement the same fix for Go as you did for Java, I think that would help.

@skuruppu skuruppu added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed 🚨 This issue needs some love. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Apr 23, 2020
@olavloite
Copy link
Contributor

@skuruppu Yes, I'll have a look.

@olavloite
Copy link
Contributor

Background info: CreateDatabase is non-idempotent and is therefore not automatically retried by the gapic client. We implemented custom retry logic for this and other non-idempotent RPCs for Java, and we'll do that for Go as well.

@flaky-bot flaky-bot bot reopened this May 15, 2020
@flaky-bot
Copy link
Author

flaky-bot bot commented May 15, 2020

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

@flaky-bot
Copy link
Author

flaky-bot bot commented May 15, 2020

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

@flaky-bot
Copy link
Author

flaky-bot bot commented May 15, 2020

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

@hengfengli
Copy link
Contributor

This is related to googleapis/go-genproto#366, which has been fixed.

@flaky-bot flaky-bot bot reopened this May 29, 2020
@flaky-bot
Copy link
Author

flaky-bot bot commented May 29, 2020

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

1 similar comment
@flaky-bot
Copy link
Author

flaky-bot bot commented May 29, 2020

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

@hengfengli
Copy link
Contributor

@olavloite This is caused by a nil pointer reference in a different test: TestClient_ReadWriteTransaction_BatchDMLAbortedHalfway. Do you have any idea about this?

@olavloite
Copy link
Contributor

Yes, while fixing a flaky test case in https://code-review.googlesource.com/c/gocloud/+/56990 I forgot to commit one of the files. Kokoro gave the green light, even though the build panicked with the same error as here, so it was merged in. It was fixed shortly after in https://code-review.googlesource.com/c/gocloud/+/56991.

@hengfengli
Copy link
Contributor

Thanks. I will close this then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the Spanner API. 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

No branches or pull requests

5 participants