Skip to content

spanner-jdbc: Fix potential flaky integration test - #6036

Merged
kolea2 merged 2 commits into
googleapis:masterfrom
olavloite:spanner-jdbc-cleanup-fix-possible-flaky-it
Aug 7, 2019
Merged

spanner-jdbc: Fix potential flaky integration test#6036
kolea2 merged 2 commits into
googleapis:masterfrom
olavloite:spanner-jdbc-cleanup-fix-possible-flaky-it

Conversation

@olavloite

Copy link
Copy Markdown
Contributor

This integration test could be flaky as it assumed that a transaction would abort an exact number of times, but fact is that Spanner could abort a transaction at any time. The test case has therefore been
changed to check that AT LEAST the expected number of aborts occurred. More than the expected number of aborts is also accepted.

This integration test could be flaky as it assumed that a transaction
would abort an exact number of times, but fact is that Spanner could
abort a transaction at any time. The test case has therefore been
changed to check that AT LEAST the expected number of aborts occurred.
More than the expected number of aborts is also accepted.
@olavloite
olavloite requested a review from kolea2August 6, 2019 14:23
@googlebotgooglebot added the cla: yes This human has signed the Contributor License Agreement. label Aug 6, 2019
@kolea2
kolea2 merged commit f7d3438 into googleapis:masterAug 7, 2019
suztomo pushed a commit to suztomo/google-cloud-java that referenced this pull request Mar 23, 2026
* fix potential flaky test
This integration test could be flaky as it assumed that a transaction
would abort an exact number of times, but fact is that Spanner could
abort a transaction at any time. The test case has therefore been
changed to check that AT LEAST the expected number of aborts occurred.
More than the expected number of aborts is also accepted.
* fix comparison
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yesThis human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@olavloite@kolea2@googlebot