If a unittest ASSERT fails after a call to enterNetwork() but before a call to exitNetwork(), the process may hang. This is because the ReplicationExecutor shutdown logic does not handle the case where all the work and event items are drained with "Cancelled" status, but the state of the NetworkInterfaceMock is still waiting for a simulated network thread to finish running.
This can be fixed by ensuring exitNetwork() is called via any exit path (using ScopeGuard, for example), but it might be more convenient to make improvements to NetworkInterfaceMock to avoid such hangs.