Great. Thanks for the info. Charlie
On Tue, Nov 2, 2010 at 11:49 AM, Michael Priemaux <602...@bugs.launchpad.net> wrote: > Charlie, > > I can confirm the latest development snapshot (2.5.9.10305) does indeed > correct the hang in our environment. > > Regards, > Michael > > -- > 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. > -- 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 Committed 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. _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
