clustermesh: improve reliability of TestClusterMesh #26370
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, TestClusterMesh is subject to possible race conditions caused by the conjoint usage of defer (i.e., to stop the identity allocator) and Cleanup (i.e., to execute the stop hook of the clustermesh subsystem). Additionally, some cluster ID reservation assertions may fail due race conditions as they are not "eventually" tested. Let's fix this possible issues to improve the reliability of the test. While at it, let's also convert it to leverage the testing framework. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
giorio94
added
kind/bug/CI
|
/test |
maintainer-s-little-helper
bot
added
the
ready-to-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, TestClusterMesh is subject to possible race conditions caused by the conjoint usage of defer (i.e., to stop the identity allocator) and Cleanup (i.e., to execute the stop hook of the clustermesh subsystem). Additionally, some cluster ID reservation assertions may fail due race conditions as they are not "eventually" tested.
Let's fix this possible issues to improve the reliability of the test. While at it, let's also convert it to leverage the testing framework.