nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Making this a timed wait would certainly guarantee stopping within a certain
time, but it might stop prematurely.

When the RemoteTestAgent is started, it immediately registeres with the
TestAgency (part of the runner) and is then given a set of tests to run.
In the case of the Gui runner, it may be asked to load and run tests
multiple times - up to the entire length of the user session.

When the runner no longer needs the agent, it signals it to stop and the
agent process exits.

Even though we can't change that wait, you've given me an idea to look
into: what happens if the runner terminates prematurely? Does that leave
the agent process executing?

Charlie

On Tue, Aug 9, 2011 at 4:51 AM, Gregory Bok <602761@xxxxxxxxxxxxxxxxxx> wrote:
> We're having similar problems in our environment.  I am wondering if the
> untimed wait on the RemoteTestAgent stopping in nunit-agent has anything
> to do with it?  Could this be turned into a timed wait?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/602761
>
> Title:
>  nunit-agent hangs after tests complete
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/602761/+subscriptions
>

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/602761/+subscriptions