Fix mock tests - futures unordered bug #1642
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.
Signed-off-by: Egor Ivkov e.o.ivkov@gmail.com
Description of the Change
unregister_peer
test, which did not wait for needed amount of timeBug Description
In
test_network
andsumeragi_with_mock
tests in several places there were dependencies on particular order of the responses thatNetwork::send
(nowNetwork::send_to_actors_on_peers
) would return. With introduction ofFuturesUnordered
the order is now random there, so tests started failing from time to time.The general problem was that code that used the function assumed a specific behavior of the function which was neither documented nor contained in a type.
Issue
#1637
Benefits
We can rely on mock tests again.
Possible Drawbacks
Usage Examples or Tests [optional]
Alternate Designs [optional]