Prevent flakiness in instance groups controller test #2996
+49
−13
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.
This test originally was added to test that creation/update/deletion of multiple nodes won't cause multiple IG controller resyncs: #2523
However as soon as node created/updated/deleted controller tries to take event out of the queue and process it, therefore if 2 actions performed one after another there is still a possibility that event processing will start before second action pushes event on the queue, which will increase
len(fakeManager.syncedNodes)value.