flaky test wait for lock cleanup #523
Open
+2
−1
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.
Related to issue #516 . I experienced different types of symptoms: Sometimes an assertion failed (assertion that remaining locks == 0), sometimes the assertion passed but there was panic or slowness elsewhere, most times the test passed fine.
My knowledge of the projects techniques is still a bit limited, so I consulted AI, but I try to use my best judgement in evaluating whether its suggestions make sense. It suggested that the test may experience a race condition regarding to how quickly the locks are cleaned up in a 2PC, and that we could wait for the lock cleanup process to let the background process finish and then check the assertions.