You would have to compare entries in the agent log file and the gui or console runner file, looking at the timestamps.
Charlie On Thu, Aug 11, 2011 at 8:04 AM, Gregory Bok <602...@bugs.launchpad.net> wrote: > I now see the issue with making that an untimed wait. The scenario you > mentioned is an interesting one however. Is that something that would > be apparent from the nunit agent log file? > > -- > 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 _______________________________________________ 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
