Fix testBreakConnection and undo workaround

[facundominguez]

The bug:

A process PA in NA monitors a process PB in NB
NA and NB are disconnected
PA tries to send a message to another process PB1 in NB
A monitor notification about PB1 death arrives to PA
No monitor notification about PB arrives to PA.

This is observed only in tests so far (MonitorNode, MonitorLiveNode, MonitorChannel from CH). These tests break connections with testBreakConnection, which doesn't deliver EventConnectionLost. If the transport delivered EventConnectionLost, then d-p would notify the death of all processes, I hope.

Instead, d-p has a patch that workarounds the problem: #246

[mboes]

These tests break connections with testBreakConnection, which doesn't deliver EventConnectionLost
isn't this a bug specific to the network-transport backend being used during tests?

[facundominguez]

Yes, probably so.

[mboes]

Then move issue to e.g. n-t-tcp? Does n-t-inmemory suffer from the same problem?

[facundominguez]

testBreakConnection is not implemented by n-t-tcp, but it is rather done in d-p-tests [1].

Addressing this probably requires implementing breakConnection in n-t-tcp (now #434). n-t-inmemory already implements it and AFAICS it does deliver EventConnectionLost.

[1]

distributed-process/distributed-process-tests/tests/runTCP.hs

Line 25 in 24cc188

, testBreakConnection = \addr1 addr2 -> do