googleapis / java-spanner Public
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.connection.it.ITTransactionRetryTest: testAbortWithExceptionOnSelect failed #685
Labels
api: spanner
Issues related to the googleapis/java-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 (d093089), 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
Dec 8, 2020
Transaction retries in the Connection API / JDBC driver could fail if the following happened: 1. The initial transaction contains a statement that returns an error that does not invalidate the transaction, such as for example a "Table not found" error, and that error is caught and handled by the application code. 2. The retry attempt tries to execute the failed statement to verify that the statement still returns the same error. If however the transaction that is used by the retry has been aborted immediately before the execution of this statement, the statement will now return Aborted instead of the original error. That would be seen as a different error than the initial error and would fail the retry attempt. When the above happens, the Aborted error in the retry should be propagated and the retry attempt should be restarted. Fixes #685
thiagotnunes
pushed a commit
that referenced
this issue
Dec 9, 2020
…688) Transaction retries in the Connection API / JDBC driver could fail if the following happened: 1. The initial transaction contains a statement that returns an error that does not invalidate the transaction, such as for example a "Table not found" error, and that error is caught and handled by the application code. 2. The retry attempt tries to execute the failed statement to verify that the statement still returns the same error. If however the transaction that is used by the retry has been aborted immediately before the execution of this statement, the statement will now return Aborted instead of the original error. That would be seen as a different error than the initial error and would fail the retry attempt. When the above happens, the Aborted error in the retry should be propagated and the retry attempt should be restarted. Fixes #685
thiagotnunes
pushed a commit
that referenced
this issue
May 6, 2021
…688) Transaction retries in the Connection API / JDBC driver could fail if the following happened: 1. The initial transaction contains a statement that returns an error that does not invalidate the transaction, such as for example a "Table not found" error, and that error is caught and handled by the application code. 2. The retry attempt tries to execute the failed statement to verify that the statement still returns the same error. If however the transaction that is used by the retry has been aborted immediately before the execution of this statement, the statement will now return Aborted instead of the original error. That would be seen as a different error than the initial error and would fail the retry attempt. When the above happens, the Aborted error in the retry should be propagated and the retry attempt should be restarted. Fixes #685
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 googleapis/java-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.
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 andI will stop commenting.
commit: d093089
buildURL: Build Status, Sponge
status: failed
Test output
The text was updated successfully, but these errors were encountered: