nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Yes, you can simply run NUnit under .NET 4.0. This is done by any of
the following
means:

1) Modifying the config file to require .NET 4.0
2) Setting the COMPLUS_Version environment variable
3) Not having any other .NET version on your machine. :-)

The details for all of these - well the first two - have already been covered n
the mail list.

However, the fix is already committed if you build from source and today's
snapshot will have it.

Charlie

On Mon, Nov 1, 2010 at 2:52 PM, Andy Lindeman <602761@xxxxxxxxxxxxxxxxxx> wrote:
> Is there any way to get NUnit to run .NET 4.0 assemblies without the
> agent?  While the agent would still be broken, in the short term, it
> would at least be a workaround for most of us, it seems.
>
> On 2010-11-01, michael.primeaux@xxxxxxxxx <602761@xxxxxxxxxxxxxxxxxx> wrote:
>> I just tried the development snapshot build 2.5.9.10304 and the hang is
>> still present. Specifically, the nunit-agent.exe process remains
>> resident. Terminating it causes the build to continue as expected.
>>
>> --
>> nunit-agent hangs after tests complete
>> https://bugs.launchpad.net/bugs/602761
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> 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.
>>
>> To unsubscribe from this bug, go to:
>> https://bugs.launchpad.net/nunitv2/+bug/602761/+subscribe
>>
>
> --
> Sent from my mobile device
>
> Andy Lindeman
> http://www.andylindeman.com/
>
> --
> 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.