Fix a flaky async payment triggerer test #2764
Merged
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.
Sometimes the
PeerReadyNotifier
for node A has not been killed before node A connects. This causes an extraGetPeerInfo
message to be sent to the switchboard and theassert(request3.remoteNodeId == remoteNodeId2)
check to fail when theGetPeerInfo
for node A comes before the one for node B. Just waiting to receive theAsyncPaymentTimeout
message does not guarantee the notifier has been stopped.If node A connects after node B then this race does not occur.
In the logs the error looked like this: