nunit-core team mailing list archive
-
nunit-core team
-
Mailing list archive
-
Message #01271
[Bug 602761] Re: nunit-agent hangs after tests complete
See Bug #612052, which has just been reactivated. Since the fix for that bug released in 2.5.8 causes the agent
process to _always_ hang around, it masks the symptoms of the current bug. We'll have to fix that one first.
--
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: 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.
References