Today when running with a non existent NCrunch cache (1 local and 2 grid nodes active, node2 is pretty and limited to 1 test task) on TeamCity, NCrunch reported errors "Code members in new coverage for test":

This error is the result of an internal consistency check performed when merging code coverage results into NCrunch's coverage database. The check basically verifies that the sequence of source files in the code coverage result is consistent with the sequence of source files in the build output.

I have never once seen this check fail before. The only thing I can think of that might cause it to fail is if somehow one of the binaries being used in your test environment is inconsistent with the rest of the session, i.e. perhaps you have an old binary from a previous session that has somehow been preserved and roped into the test environment. If you're able to reproduce this problem in a way that you can share with me, I should be able to dig deeper and figure out what is happening.

It is happening quite often on my CI build (with a large solution unfortunately) which is quite annoying because the build might take 30minutes and then fail due to this error and have to be re-executed without NCrunch cache (re-executing all tests), can I send create some NCrunch verbose output logs or whatever to help troubleshooting it?

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.