spanner: TestIntegration_DML failed #2486
Assignees
Labels
api: spanner
Issues related to the Spanner 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
|
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 (7641218), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge). |
olavloite
added a commit
that referenced
this issue
Jun 24, 2020
A read/write transaction should always return any error to the transaction runner and let it determine whether it should be returned to the user application, or it should cause a transaction retry. Failing to do so, can cause the transaction to fail sometimes with an Aborted error. Fixes #2486
olavloite
added a commit
that referenced
this issue
Jun 25, 2020
A read/write transaction should always return any error to the transaction runner and let it determine whether it should be returned to the user application, or it should cause a transaction retry. Failing to do so, can cause the transaction to fail sometimes with an Aborted error. Fixes #2486
This was referenced Jul 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: #2160 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: 7641218
buildURL: Build Status, Sponge
status: failed
The text was updated successfully, but these errors were encountered: