Internally, NCrunch has a concept of a 'Primary' build result.

The Primary build result is considered to be the result of the first build to complete running for a particular version of the source code for a project. It is the only result that NCrunch considers when reporting build data in the logs.

If you are working over a grid of 3 machines, NCrunch will build a changed project 3 times - one on each machine. The first machine to return a result has the responsibility of reporting the primary result. If the other build results are inconsistent to this, NCrunch will still amend the reported result in the Tests Window so that you are aware of this, but it will otherwise continue as normal since it has the build result it requires.

In this case you've described above, the result you're seeing is probably a non-primary build result. It isn't relevant, since NCrunch has already been told that the build has passed. The HTML results report does specify the node that provided the primary build result if you drill into an individual project inside the 'Build Results' tab.

So I guess the issue here is that unlike the Tests Window, NCrunch is not including the non-primary build results in the HTML export where they differ from the primary result. This will need to be fixed. Thanks for making me aware of it.