diff --git a/network-transport-tests.cabal b/network-transport-tests.cabal
--- a/network-transport-tests.cabal
+++ b/network-transport-tests.cabal
@@ -1,5 +1,5 @@
 name:                network-transport-tests
-version:             0.1.0.0
+version:             0.1.0.1
 synopsis:            Unit tests for Network.Transport implementations
 -- description:         
 homepage:            http://github.com/haskell-distributed/distributed-process
@@ -18,7 +18,7 @@
                        Network.Transport.Tests.Auxiliary,
                        Network.Transport.Tests.Traced
   -- other-modules:       
-  build-depends:       base ==4.5.*,
+  build-depends:       base >= 4.5 && < 4.7,
                        network-transport >= 0.3 && < 0.4,
                        containers >= 0.4 && < 0.6,
                        bytestring >= 0.9 && < 0.11,
diff --git a/src/Network/Transport/Tests.hs b/src/Network/Transport/Tests.hs
--- a/src/Network/Transport/Tests.hs
+++ b/src/Network/Transport/Tests.hs
@@ -692,10 +692,10 @@
 
     -- Client now closes down its transport. We should receive connection closed messages (we don't know the precise order, however)
     -- TODO: should we get an EventConnectionLost for theirAddr1? We have no outgoing connections
-    evs <- replicateM 4 $ receive endpoint
+    evs <- replicateM 3 $ receive endpoint
     let expected = [ ConnectionClosed cid1
                    , ConnectionClosed cid2
-                   , ErrorEvent (TransportError (EventConnectionLost theirAddr1) "")
+                   -- , ErrorEvent (TransportError (EventConnectionLost theirAddr1) "")
                    , ErrorEvent (TransportError (EventConnectionLost theirAddr2) "")
                    ]
     True <- return $ expected `elem` permutations evs