nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

You'd have to build it from the latest source. It's fairly trivial to
install bazaar
and get the latest source. See the developer FAQ on the wiki.

Charlie

On Mon, Sep 27, 2010 at 10:23 AM, Ace Olszowka
<602761@xxxxxxxxxxxxxxxxxx> wrote:
> Thanks Charlie for getting that fix committed, is there any place where
> I might find a nightly development build to test the fix? or is my best
> bet to try and build locally? I'll admit I'm pretty new to Launchpad and
> I'm not quite sure how to grab the latest version of the source.
>
> --
> 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.
>

-- 
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.