We are seeing a problem on some machines where we get an NPE in
JUnitTestClassProcessor line 64. It appears that sometimes executor is not set
before processTestClass is called. I'm not quite sure I'm following the logic
here, but it looks like a possible problem with the ForkingTestClassProcessor.
Does the call on line 71 of ForkingTestClassProcessor (workerProcess.start())
end up calling worker.startProcessing in another thread? If so, then I think
there is a race condition. JUnitTestClassProcessor.processTestClass can be
called before JUnitTestClassProcessor.startProcessing.
My line numbers (and problem) are referencing a version from Monday (commit
89b9abf8f ).
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
