ITReadOnlyTxnTest is flaky with multiplexed sessions #3132
Labels
api: spanner
Issues related to the googleapis/java-spanner API.
type: process
A process-related concern. May include testing, release, or the like.
Using a min-read-timestamp is not allowed with a multi-use read-only transaction. This is also checked by the
ITReadOnlyTxnTest
. However, the error that is returned when using multiplexed sessions can be different than the current expectation. The reason is that if the transaction is started before the multiplexed session has been created, the code flow uses a waiter. This waiter will return the error as aSpannerException
, while the direct code flow will return anIllegalArgumentException
. That causes the following flaky test failure in some cases (note that in a production situation the difference between the two errors are not really relevant, both indicate a programming error that needs to be fixed in code):The text was updated successfully, but these errors were encountered: