CNDB-13238: Fix flaky CounterLockManagerTest interruption tests that don't properly wait for a finally block to complete (#1820) #1879
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.
What is the issue
The final assert in this test checks that the locks have been cleaned up. These need to be released twice; once by the main thread, and once in the finally block of a thread started by the test. The test waits for a CompletableFuture to be set by this thread, but it does not wait for the finally block to finish.
What does this PR fix and why was it fixed
Join on the other thread in the test, which ensures the finally block completes before the last assertion that checks all refs to the locks have been released.