We are seeing what might be a related issue in that the agent hangs and displays a Segmentation Fault error message. We are able to reproduce this on a single Windows 2003 R2 machine; however, other machines with the same operating system do not hang and/or yield a segmentation fault. Like the others, we are running the x86 version and are using 2.5.9.10348. Also, the failures inconsistently happen for the same set of tests.
If there is any more information I can provide, please 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
