The bug was fixed for many people but then re-opened because others were still seeing a problem. I don't believe you have reported it before, so can you provide info on your environment and how you are running NUnit?
Charlie On Wed, Mar 16, 2011 at 10:50 AM, Aaron Jensen <[email protected]> wrote: > What's the status on this bug. It is causing our organization a great > deal of pain. We have to manually log into our build servers at least > once a day to clear out all the nunit-agent.exe processes that didn't > close properly. It is very frustrating. > > -- > 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 > -- 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. _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : [email protected] Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
