nunit-core team mailing list archive

[Ace Olszowka <602761@xxxxxxxxxxxxxxxxxx>]

Just a post for anyone still following this: We ended up just forcing
the nunit-console and nunit-gui to run on the .NET Framework 4.0 as
suggested by Charlie above. This can be done by the following (since it
didn't seem to already be posted in this thread):

1. Open each app.config file in the text editor of your choice (we did nunit.exe, nunit-x86.exe, nunit-console.exe nunit-console-x86.exe)
2. Right below the configuration append the following:
  <startup>
     <supportedRuntime version="v4.0.30319"/>
  </startup>
3. Save the file and restart Nunit

Note that this will force nunit to run with the .net framework
v4.0.30319 all the time, for us this isn't a big deal as we have
separate build environment for each version of the .net framework on
which we deploy against.

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