nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

This particular bug is fixed, but "hanging nunit-agent" is an extremely
general symptom. If anyone sees the problem again, please start a new
bug that includes the precise details of the situation where it happens:
32- versus 64-bit, .NET 4.0 versus 2.0, etc.

** Changed in: nunitv2
       Status: In Progress => Fix Committed

** Changed in: nunitv2
       Status: Fix Committed => Fix Released

-- 
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 Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/602761/+subscriptions