Run testDeleteRowsConcurrently sequentially for better reliability #23916
+3
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes: #21862
Currently test repetition runs in parallel which can cause query exceed 20s timeout, it's especially visible in case of Glue tests.
Analysis showed that most time is spend on:
glueClient.updateTable
, when executed in parallel and failing update throwsConcurrentModificationException
, is about 10sIf query which consumed time on finishMerge also encounters ConcurrentModificationException, 20s is exceeded and test fails.
Running tests sequentially removes first problem and makes test more reliable.
Additional context and related issues
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text: