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

datastore: TestIntegration_GetWithReadTime failed #6938

Closed
flaky-bot bot opened this issue Oct 26, 2022 · 7 comments · Fixed by #6941, #6979 or #7004
Closed

datastore: TestIntegration_GetWithReadTime failed #6938

flaky-bot bot opened this issue Oct 26, 2022 · 7 comments · Fixed by #6941, #6979 or #7004
Assignees
@triplequark
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.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Oct 26, 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: 9240741
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:222: client.Get: rpc error: code = InvalidArgument desc = timestamp cannot have more than microseconds precision
@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 Oct 26, 2022
@product-auto-label product-auto-label bot added the api: datastore Issues related to the Datastore API. label Oct 26, 2022
@telpirion telpirion removed type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Oct 26, 2022
@telpirion telpirion mentioned this issue Oct 26, 2022
Merged
@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 26, 2022

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

Test output
    integration_test.go:222: client.Get: rpc error: code = InvalidArgument desc = timestamp cannot have more than microseconds precision

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 27, 2022

commit: 900afc4
buildURL: Build Status, Sponge
status: failed

Test output
    integration_test.go:222: client.Get: rpc error: code = InvalidArgument desc = timestamp cannot have more than microseconds precision

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 27, 2022

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

Test output
    integration_test.go:222: client.Get: rpc error: code = InvalidArgument desc = timestamp cannot have more than microseconds precision

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 27, 2022

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

Test output
    integration_test.go:222: client.Get: rpc error: code = InvalidArgument desc = timestamp cannot have more than microseconds precision

@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 27, 2022

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

Test output
    integration_test.go:222: client.Get: rpc error: code = InvalidArgument desc = timestamp cannot have more than microseconds precision

@flaky-bot flaky-bot bot reopened this Oct 27, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented Oct 27, 2022

Looks like this issue is flaky. 😟

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

A human should fix and close this.

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

Test output
    integration_test.go:222: client.Get: datastore: no such entity

@flaky-bot flaky-bot bot added flakybot: flaky Tells the Flaky Bot not to close or comment on this 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 27, 2022
@telpirion telpirion removed type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Oct 28, 2022
@telpirion telpirion mentioned this issue Nov 2, 2022
Merged
@telpirion telpirion assigned triplequark and unassigned telpirion Nov 4, 2022
@flaky-bot flaky-bot bot reopened this Nov 7, 2022
@flaky-bot flaky-bot bot added 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 7, 2022
@flaky-bot
Copy link
Author

flaky-bot bot commented Nov 7, 2022

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

Test output
    integration_test.go:222: client.Get: datastore: no such entity

@telpirion telpirion removed the type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. label Nov 8, 2022
@telpirion telpirion removed the priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. label Nov 8, 2022
@telpirion telpirion mentioned this issue Nov 8, 2022
Merged
@flaky-bot flaky-bot bot mentioned this issue Feb 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@triplequark triplequark

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.
Projects
None yet
Milestone
No milestone
2 participants
@telpirion @triplequark