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

datastore: TestIntegration_LargeQuery failed #6514

Closed
flaky-bot bot opened this issue Aug 14, 2022 · 3 comments · Fixed by #6610
Closed

datastore: TestIntegration_LargeQuery failed #6514

flaky-bot bot opened this issue Aug 14, 2022 · 3 comments · Fixed by #6610
Assignees
Labels
api: datastore Issues related to the Datastore 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. status: investigating The issue is under investigation, which is determined to be non-trivial.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Aug 14, 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: 370e23e
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:623: Count(limit=800 offset=0) returned 500, want 800
    integration_test.go:623: Count(limit=500 offset=500) returned 0, want 300
    integration_test.go:623: Count(limit=-1 offset=500) returned 0, want 300
    integration_test.go:623: Count(limit=1000 offset=100) returned 400, want 700
    integration_test.go:623: Count(limit=-1 offset=0) returned 500, want 800
    integration_test.go:623: Count(limit=501 offset=0) returned 500, want 501
    integration_test.go:623: Count(limit=1600 offset=0) returned 500, want 800
    integration_test.go:623: Count(limit=-1 offset=100) returned 400, want 700
    integration_test.go:702: count=200, limit=-1, offset=500: it.Next from cursor: no more items in iterator, want nil
    integration_test.go:702: count=500, limit=-1, offset=0: it.Next from cursor: no more items in iterator, want nil
    integration_test.go:633: GetAll(limit=500 offset=500) returned 0, want 300
    integration_test.go:633: GetAll(limit=-1 offset=500) returned 0, want 300
    integration_test.go:633: GetAll(limit=-1 offset=0) returned 500, want 800
    integration_test.go:633: GetAll(limit=800 offset=0) returned 500, want 800
    integration_test.go:633: GetAll(limit=1000 offset=100) returned 400, want 700
    integration_test.go:637: GetAll(limit=501 offset=0) got[500].I == 514; want 500
@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 Aug 14, 2022
@product-auto-label product-auto-label bot added the api: datastore Issues related to the Datastore API. label Aug 14, 2022
@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Aug 14, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented Aug 14, 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 (370e23e), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@telpirion telpirion 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. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Sep 1, 2022
@telpirion
Copy link
Contributor

Investigating this now.

@telpirion telpirion added the status: investigating The issue is under investigation, which is determined to be non-trivial. label Sep 1, 2022
@telpirion
Copy link
Contributor

telpirion commented Sep 1, 2022

I think that there might be an issue with concurrent goroutines, multiple test runs (processes), and the placement of the query cursor. I'm going to try to break the failing test into three parts rather than running them concurrently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: datastore Issues related to the Datastore 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. status: investigating The issue is under investigation, which is determined to be non-trivial.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant