Hey Charlie, I just got latest and compiled the code (revision 3236)
and it looks like this issue is still present. I am running Nunit-
console as part of a Nant build and now every test fixture is leaving an
nunit-agent process running. I am using .net 4.0 framework and running
on a Windows server R2 machine.
My NAnt lines are all in this format :
<exec program="${NunitEXE}" failonerror="false" timeout="3000000">
<arg line="/run:TestClasses.BTests ${TestDLL}
/framework=4.0.30319 /noshadow /nologo /labels /out:${TextOutputPath}\BTest.txt
/xml:${LogFilePath}\TestBTest.xml" />
</exec>
Any help would be greatly appreciated. Is there another way to run nunit
to work around this issue?
--
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
