Test fail with no explanation

maoz's Avatar


19 Apr, 2017 06:18 AM


One of the tests in my project keeps failing and there's no information except the error below.
I assume the machine is out of resources. Is there anyway to understand why?

1) Error : C:\projects\abot\Abot.Tests.Unit\bin\Debug\Abot.Tests.Unit.dll
An existing connection was forcibly closed by the remote host
Server stack trace:
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Runtime.Remoting.Channels.SocketStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket(Byte[] buffer, Int32 offset, Int32 count)
   at System.Runtime.Remoting.Channels.SocketHandler.Read(Byte[] buffer, Int32 offset, Int32 count)
   at System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes(Byte[] buffer)
   at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble()
   at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOperation(UInt16& operation)
   at System.Runtime.Remoting.Channels.Tcp.TcpClientSocketHandler.ReadHeaders()
   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at NUnit.Engine.ITestEngineRunner.Run(ITestEventListener listener, TestFilter filter)
   at NUnit.Engine.Runners.ProcessRunner.RunTests(ITestEventListener listener, TestFilter filter)

This is the build:

  1. Support Staff 1 Posted by Ilya Finkelshte... on 19 Apr, 2017 07:05 PM

    Ilya Finkelshteyn's Avatar

    Machine is not out of resources. I cloned your repository and reproduced build error. When I connect to build worker with RDP, I see normal load until this exception thrown. At that moment 1 of 2 CPU Cores is being totally occupied by Windows Error Reporting (werfault) and the following message appears in Application log:

    Faulting application name: nunit-agent.exe, version:, time stamp: 0x58bdfcf4
    Faulting module name: unknown, version:, time stamp: 0x00000000
    Exception code: 0xc00000fd
    Fault offset: 0x00007ff90381e8d6
    Faulting process id: 0x694
    Faulting application start time: 0x01d2b93bd74be517
    Faulting application path: C:\Tools\NUnit3\nunit-agent.exe
    Faulting module path: unknown
    Report Id: 5efba4f1-252f-11e7-817b-00155d20c03a
    Faulting package full name: 
    Faulting package-relative application ID:
    Which means that it is stack overflow in nunit-agent.exe. I tried previous nunit versions and also using command line with --workers=1 setting. Nothing helps.

    I wonder if it works locally for you from command line. And if yes, what specific command do you run and what specific nunit version do you use?


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac