NCrunch Console hanging under TeamCity (possible cause)

We've had issues with NCrunch console hanging during test runs. We're running it through a TeamCity server. It always seem to hang toward the very end of the test run, and we then have to tell TeamCity to terminate the job or else it continues indefinitely. These are long SpecFlow+Selenium web app end-to-end test runs that take several hours to complete, and always nearly all tests would be completed before the hanging.

I unfortunately don't have enough time at the moment to properly troubleshoot this, but we've made an anecdotal observation that could possibly be a clue if others are investigating the same issue. If we have the console machine also configured as a grid node for the console run, we often (maybe always) get the hanging behavior. When we don't do this, it seems we don't get the hanging behavior!

Are there known issues around this?

Hi, thanks for sharing this issue.

An important consideration here is to establish the source of the hanging, which is best done using the logs from the console tool run. There are two ways this can hang:

1. A test is running overtime and cannot be aborted
2. The engine is failing to correctly consider a completion status and is stuck after all tests are run

I would hope that the second case is now impossible, as there have been many fixes targeted towards this issue over the years, but it is still a very complex area of NCrunch.

Are there any tests running at the time the console tool hangs?