nunit-core team mailing list archive

[Anders Juul <602761@xxxxxxxxxxxxxxxxxx>]

Hi all,

I had same issue, fell over this discussion and upgraded my nunit from
2.5.8 to NUnit-2.5.9.10344 (first non-official release of any kind I
ever install on a work machine!) - and it works like a charm.

It just struck me how I take it for granted that nunit works - and I now
appreciate your effort more.

Thanks for providing the best test framework!

Anders,
Denmark

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/602761

Title:
  nunit-agent hangs after tests complete

Status in NUnit V2 Test Framework:
  Fix Committed

Bug description:
  If a test fixture is being run in a different process (using nunit-agent), every now and then nunit-console will print out the results of the tests and exit, but the nunit-agent process will hang around indefinitely.

I believe the issue is with .NET Remoting, specifically the TestAgent/RemoteTestAgent.Stop operations.  Stop is marked as a one-way call, which tells the .NET Framework that the call can be completed asynchronously.  However, this also means that when nunit-console exits immediately after calling Stop, the message may never actually be sent to the nunit-agent.

Recommend removing the OneWay attribute so that the call is completed synchronously and thereby guaranteed to be delivered.