This is an error that's being kicked up at discovery time. At this point in the process, error capture and handling is much less sophisticated under NUnit v2. NCrunch recognises that there is a problem with the test, but the error itself isn't reported. The issue here is that NUnit v2 does not have a formal API for test runners, so when things go wrong there is no consistent way to respond to issues.
Fixing this problem isn't really feasible, since NUnit v2 is itself several years out of date now and the nature of its design means that fixing edge cases like this just isn't worth the risk. NUnit v3 has an entirely new adapter with a formal API and error handling that is much better suited to this kind of thing. If this problem is causing you pain, I recommend upgrading to NUnit v3.
