fix: Fix flakeyness of TestProvisionerd/ReconnectAndComplete #5169
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.
I noticed this sleep was added to another test in #5136 as well. Since
TestProvisionerd/ReconnectAndComplete
was constantly flaking, I added it there as well. It seems to have alleviated the issue but I don't really even understand this test.Why is this issue triggered via memDRPC and not yamux? Maybe because memDRPC is faster? Or perhaps isn't handling some edge case in the same way causing "reconnect" to fail.
Logs on fail:
Logs on success:
We can see that the error pops up before
connected
when it does, i.e. we tried to do something whilst waiting for the connection to be (re)established.