[MonoDevelop] RemotingException: Unix transport error when Running Tests

[Scott Willeke]

First, this is not when starting MD. It starts just fine. The problem occurs when running unit tests via the "Unit Tests" window. If I build from trunk it seems to happen constantly on all tests, but in the 2.2 release it happens on nearly all unit tests but some work. Using the 2.2 download, the most simple project with a single simple test it works.

I've found that the root of the problem is when it calls the NUnit.Core.RemoteTestRunner.Run method from the MonoDevelop.NUnit.External.NUnitTestRunner.Run method. 

I have debugged this exhaustively and don't know what else to look for. I suspect I'm missing something simple. Can someone point me in the right direction?


I'm on an intel OSX 10.6.2.
I will greatly appreciate any advice or direction on how to track the problem down.




A stack trace from the "Internal Message Log" in 2.2 is below:



Error - 20:51:59 - System.Runtime.Remoting.RemotingException: Unix transport error.

Server stack trace: 
  at Mono.Remoting.Channels.Unix.UnixMessageIO.ReceiveMessageStatus (System.IO.Stream networkStream, System.Byte[] buffer) [0x0000f] in /private/tmp/monobuild/build/BUILD/mono-2.6.1/mcs/class/Mono.Posix/Mono.Remoting.Channels.Unix/UnixMessageIO.cs:59 
  at Mono.Remoting.Channels.Unix.UnixClientTransportSink.ProcessMessage (IMessage msg, ITransportHeaders requestHeaders, System.IO.Stream requestStream, ITransportHeaders& responseHeaders, System.IO.Stream& responseStream) [0x0004f] in /private/tmp/monobuild/build/BUILD/mono-2.6.1/mcs/class/Mono.Posix/Mono.Remoting.Channels.Unix/UnixClientTransportSink.cs:172 
  at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage (IMessage msg) [0x0006c] in /private/tmp/monobuild/build/BUILD/mono-2.6.1/mcs/class/System.Runtime.Remoting/System.Runtime.Remoting.Channels/BinaryClientFormatterSink.cs:157 

Exception rethrown at [0]: 
 ---> System.Runtime.Remoting.RemotingException: Connection closed
  at Mono.Remoting.Channels.Unix.UnixMessageIO.StreamRead (System.IO.Stream networkStream, System.Byte[] buffer, Int32 count) [0x0002c] in /private/tmp/monobuild/build/BUILD/mono-2.6.1/mcs/class/Mono.Posix/Mono.Remoting.Channels.Unix/UnixMessageIO.cs:99 
  at Mono.Remoting.Channels.Unix.UnixMessageIO.ReceiveMessageStatus (System.IO.Stream networkStream, System.Byte[] buffer) [0x00000] in /private/tmp/monobuild/build/BUILD/mono-2.6.1/mcs/class/Mono.Posix/Mono.Remoting.Channels.Unix/UnixMessageIO.cs:57 
  --- End of inner exception stack trace ---
  at Mono.Remoting.Channels.Unix.UnixMessageIO.ReceiveMessageStatus (System.IO.Stream networkStream, System.Byte[] buffer) [0x0000f] in /private/tmp/monobuild/build/BUILD/mono-2.6.1/mcs/class/Mono.Posix/Mono.Remoting.Channels.Unix/UnixMessageIO.cs:59 
  at Mono.Remoting.Channels.Unix.UnixClientTransportSink.ProcessMessage (IMessage msg, ITransportHeaders requestHeaders, System.IO.Stream requestStream, ITransportHeaders& responseHeaders, System.IO.Stream& responseStream) [0x0004f] in /private/tmp/monobuild/build/BUILD/mono-2.6.1/mcs/class/Mono.Posix/Mono.Remoting.Channels.Unix/UnixClientTransportSink.cs:172 
  at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage (IMessage msg) [0x0006c] in /private/tmp/monobuild/build/BUILD/mono-2.6.1/mcs/class/System.Runtime.Remoting/System.Runtime.Remoting.Channels/BinaryClientFormatterSink.cs:157