filecoin-project/go-f3

Test message drop once re-broadcast is integrated

Closed this issue · 1 comments

Once the re-broadcast is integrated, F3 should be resilient to message drop, where some messages are never delivered. Update the simulation to have a configuration parameter for percentage of message drop and assert that consensus is achieved eventually, i.e. the instance should still result in a decision but may take longer.

Done as part of #414