We have been trying out the console runner against a grid of 8 test runners. We frequently find that the console output pauses somewhere along the way, and at that point there appears to be no activity on the grid nodes or the local machine. If we do nothing, nothing further happens for at least 30 minutes (at which point our patience ran out :) ). But if we hit CTRL-C at any moment during the pause, the console runner immediately springs back to life, with more output appearing in the console and work activity appearing on the nodes.
Exact reproduction steps for this are hard to come up with, but the behavior is happening frequently and on different test running machines.
Is there a way to send the console app's logging to a file?
Remco suggested to me that this might be a buffering issue with the console output. Is there a way to have less output from the console?
