nunit-core team mailing list archive

[Hawkeye Parker <602761@xxxxxxxxxxxxxxxxxx>]

We're still seeing the nunit-agent process hang (indefinitely) in
2.5.9.10348, even with successful runs:

.\NUnit\nunit-console.exe /fixture=Autodesk.Buzzsaw.Test.UnitTest.TestCases.UnitTest Autodesk.Buzzsaw.UnitTest.dll
NUnit version 2.5.9.10348

Tests run: 1, Errors: 0, Failures: 0, Inconclusive: 0, Time: 9.6719988 seconds
  Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0

A few notes:
-Each time I run, a new nunit-agent spawns and hangs.  I have to manually kill the processes.
-The dll which hosts these "unit tests" is big.  Not a lot of tests, per se, but a lot of code:  the tests are really high-level, automated integration tests.
-Running through the GUI is different:  after running the tests, if I close the GUI, the nunit-agent process stays open for ~10 secs. and then exits.  If I load a smaller project into the GUI, then run and exit, nunit-agent exits immediately.

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