Don't if it's exactly that bug but found a problem in PNUnit that cause PNUnit to hang at NotifyResult. In Agent, PNUnitTestRunner.cs if a exception occur in the finally @ ThreadProc:124, the agent just seems to hang or crash without error.
In my case if I put a invalid test name in my *.conf file, FindResult return null for result and BuildResult check for IsSuccess causing NullReferenceException
//Fix for my case
--return null @ FindResult:196
++return result @ FindResult:196
Also comparing to PNUnit version I have downloaded your PNUnit seems to be outdated, the PNUnitTestRunner.cs is signicantly different.
Don't if it's exactly that bug but found a problem in PNUnit that cause PNUnit to hang at NotifyResult. In Agent, PNUnitTestRunner.cs if a exception occur in the finally @ ThreadProc:124, the agent just seems to hang or crash without error.
In my case if I put a invalid test name in my *.conf file, FindResult return null for result and BuildResult check for IsSuccess causing NullReferenceEx ception
//Fix for my case
--return null @ FindResult:196
++return result @ FindResult:196
Also comparing to PNUnit version I have downloaded your PNUnit seems to be outdated, the PNUnitTestRunner.cs is signicantly different.