We are sharing NCrunch nodes between multiple TeamCity test run builds
NCrunch is holding up the TeamCity test run waiting on a node that is not running a test.
That node is waiting to build the solution but is busy with another test from a separate TeamCity test run build.
How can we tell the NCrunch nodes to stop building the solution when all of the tests are already being/been run by other NCrunch nodes?
Also, this example test run only had 7 tests.
There are 11 NCrunch nodes in this pool.
So 4 will definitely not be needed, but they all synchronise and build the test solution.
How do we tell the NCrunch nodes that we only need the first 7 available nodes to synchronise and build the test solution?
It seems that would make for more efficient usage of the nodes, so that the next test build doesnt have to wait for the 4 unused nodes to synchronise and building the test solution that they wont use.
in the logs it shows it NCrunch is sending instructions for 1 task 4 minutes after all the tests have completed
Quote:[06:37:33][Step 8/13] [Core-382] Sending processing instructions to node N015 for 1 tasks
[06:37:52][Step 8/13] [Core-371] Grid node N015 reports task completed: [LocalBuildTask: [SnapshotComponent: Specifications.Testing, 0, 19297194], ProcessingSucceeded, N015, c48e267c-44c9-49ad-879f-9aa46eebf8ef]
[06:37:52][Step 8/13] [Core-371] Sending processing instructions to node N015 for 1 tasks
[06:37:54][Step 8/13] [Core-225] Grid node N015 reports task completed: [LocalBuildTask: [SnapshotComponent: Performance.Testing, 1, 56438004], ProcessingSucceeded, N015, 025377e3-848a-43dd-82c1-f76b8ac3f573]
[06:37:55][Step 8/13] [?-1] Reporting engine execution results