nunit-core team mailing list archive

[JC <602761@xxxxxxxxxxxxxxxxxx>]

We have the same problem in our organization. We use a single test list
for all our different test levels, so a given fixture sometime will
called with a test level for which there is no test case. I've found
that the problem of unit-agent.exe hanging happen most of the time on
fixtures like those that contains 0 test for the current test level.

Would it be possible for the runner to start and exit too fast for the
unit-agent.exe to receive the 'end' signal ?

-- 
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:
  In Progress

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