We run on Windows 2008 R2. Our continuous integration server is CruiseControl 1.6. We run NUnit directly from our MSBuild scripts and under NCover 3.4. Here is how we invoke NUnit outside of NCover:
nunit-console.exe Assembly.dll Assembly2.dll /noshadow /framework=4.0 /domain=Single /include="Unit Test" /xml=NUnitResults.xml Executing through NCover is a little more complicated. Our build script creates a temporary NUnit project which is then fed into NCover using the MSBuild task's that ship with NCover. We get zombie/orphaned nunit-agent.exe processes regardless of how NUnit gets run. We are working around the problem by creating a pre-build target that kills any nunit-agent.exe processes that are misbehaving. -- 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
