spanner: TestIntegration_UpdateDuringRead failed #5800
Assignees
Labels
api: spanner
Issues related to the Spanner API.
external
This issue is blocked on a bug with the actual product.
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: 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
bot
added
flakybot: issue
flaky-bot
bot
added
the
flakybot: flaky
|
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 (d6dea46), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge). |
|
Seems external, closing this to see if it happens again. |
|
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: 23ea358 Test output integration_test.go:1062: 1: ReadOnlyTransaction.ReadRow before write returns error: spanner: code = "FailedPrecondition", desc = "Read-only transaction timestamp 2022-04-05T10:21:24.162349Z has exceeded the maximum timestamp staleness", want NotFound
integration_test.go:1072: 1: ReadOnlyTransaction.ReadRow after write returns error: spanner: code = "FailedPrecondition", desc = "Read-only transaction timestamp 2022-04-05T10:21:24.162349Z has exceeded the maximum timestamp staleness", want NotFound
integration_test.go:1062: 2: ReadOnlyTransaction.ReadRow before write returns error: spanner: code = "FailedPrecondition", desc = "Read-only transaction timestamp 2022-04-05T10:21:26.341551Z has exceeded the maximum timestamp staleness", want NotFound
integration_test.go:1072: 2: ReadOnlyTransaction.ReadRow after write returns error: spanner: code = "FailedPrecondition", desc = "Read-only transaction timestamp 2022-04-05T10:21:26.341551Z has exceeded the maximum timestamp staleness", want NotFound |
rahul2393
added
the
external
This was referenced Jun 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This test failed!
To configure my behavior, see the Flaky Bot documentation.
If I'm commenting on this issue too often, add the
flakybot: quietlabel andI will stop commenting.
commit: d6dea46
buildURL: Build Status, Sponge
status: failed
Test output
integration_test.go:1062: 1: ReadOnlyTransaction.ReadRow before write returns error: spanner: code = "FailedPrecondition", desc = "Read-only transaction timestamp 2022-03-27T07:28:55.255059Z has exceeded the maximum timestamp staleness", want NotFound integration_test.go:1072: 1: ReadOnlyTransaction.ReadRow after write returns error: spanner: code = "FailedPrecondition", desc = "Read-only transaction timestamp 2022-03-27T07:28:55.255059Z has exceeded the maximum timestamp staleness", want NotFound integration_test.go:1062: 2: ReadOnlyTransaction.ReadRow before write returns error: spanner: code = "FailedPrecondition", desc = "Read-only transaction timestamp 2022-03-27T07:28:55.734110Z has exceeded the maximum timestamp staleness", want NotFound integration_test.go:1072: 2: ReadOnlyTransaction.ReadRow after write returns error: spanner: code = "FailedPrecondition", desc = "Read-only transaction timestamp 2022-03-27T07:28:55.734110Z has exceeded the maximum timestamp staleness", want NotFoundThe text was updated successfully, but these errors were encountered: