Hey, I have the same problem only in a more controlled environment. In the AutoTest.Net project we are hosting NUnit inside our own runner. Right now inside our runner we are issuing a GetCurrentProcess().Kill() to be able to shut down our process. If I remove this line I get the hang issue and our runner never exits. It happens consequently when running tests in the AutoTest.Net project with our own runner. If you guys want to investigate the source is at https://github.com/acken/AutoTest.Net. To get and use just pull, run build.bat and then deploy.bat. All you need is in the ReleaseBinaries folder. I'm running on a 32bit system.
If I can do anything to help you guys out just let me know. -- 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 : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
