Hi Ilya,

Thanks for reporting this problem. Please accept my apologies for the website being down – it seemed to hit some kind of DB related problem overnight and has since recovered.

It looks to me like there is an inconsistency here being caused by a race condition in the test. The test starts a number of different threads which execute in the background while the primary thread waits with a sleep.

When performing multi-threaded testing, it’s extremely important that the execution of all background threads is performed within the boundary of the foreground test thread. Where this isn’t the case, NCrunch will misreport coverage information because the background threads then become bounded by tests executed later in the run, and the coverage data isn’t allocated correctly. See here for more information - http://www.ncrunch.net/documentation/considerations-and-constraints_multi-threaded-tests.

The log file contained no unusual information about engine activity.

Does increasing the size of the Sleep make any difference?



Cheers,

Remco