nunit-core team mailing list archive

[Andy Lindeman <602761@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: nunitv2
     Importance: Undecided
         Status: New

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

Status in NUnit V2 Test Framework: New

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.