nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

** Tags added: pnunit

-- 
PNUnit Hangs on Simple Test
https://bugs.launchpad.net/bugs/498689
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: Triaged

Bug description:
There's currently a problem with pNUnit where the notification of results
simply hangs. To repro,

1) Build latest source with nant build.
2) Change to build\net\2.0\debug, assuming you're on
a windows machine. I haven't verified this problem
on linux yet.
3) copy agent.log.conf to launcher.log.conf
4) runpnunit.bat

The agent window shows the following:

INFO PNUnit.Agent.PNUnitAgent - Registering channel on port 8080 INFO
PNUnit.Agent.PNUnitAgent - RunTest called for Test Testing, AssemblyName p
nunit.tests.dll, TestToRun TestLibraries.Testing.EqualTo19 INFO
PNUnit.Agent.PNUnitTestRunner - Spawning a new thread INFO
PNUnit.Agent.PNUnitTestRunner - Thread entered for Test Testing:TestLibrar
ies.Testing.EqualTo19 Assembly pnunit.tests.dll INFO
PNUnit.Agent.PNUnitTestRunner - Notifying the results

The launcher window shows this:

INFO launcher - Test 1 of 1
DEBUG launcher - Thread created for TestGroup Testing with 1 tests INFO
launcher - Starting Testing test Testing on localhost:8080 DEBUG launcher -
Thread going to wait for results for TestGroup Testing

It appears that NotifyResult() in the launcher is never entered. A problem
with remoting?

[From SF:2766410]

Comment from SF:

As a temporary fix, pnunit.tests.dll is in the same directory as
pnunit-agent.exe and pnunit-launcher.exe. The nunit.framework and
pnunit.framework assemblies are being copied to the
same directory.

PNUnit should allow the same flexibility of appbase and probing paths that
NUnit itself supports.