Fix flaky test_same_subnet_unsubscription() #8609
Open
+17
−25
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.
Issue Addressed
#7573
Why
the race condition seems due to the usage of
is_subscribed()instead ofis_subscribed_permanent(), which was not following the comment's desired behaviour sinceis_subscribed()considers both permanent and temporary subscriptions.// If we are permanently subscribed to this subnet, we won't see a subscribe messageso, previously, we could be taking the
ifbranch for a temporary subscriptiondiscarding
Subscribeand potentiallyUnsubscribeevents; thus, when reachingthe expected
Unsubscribecould have been discarded already, resulting in [].Fix
refactored the test to use a more deterministic approach following the other tests and removed
is_subscribed()since we take the same route by checkingis_subscribed_permanent()firstResults