Option for unbuffered stdout for cgreen-runner

[tpecar]

When debugging complex tests that also output some additional debug info (custom state printouts, library debug output, etc.), it would be beneficial if the cgreen-runner process could configure its stdout as unbuffered (before forking into individual tests).

This could be done either via switch or environment variable.

[thoni56]

Could you give an explicit example/test case of output where this would make a difference? If the debug output is also buffered would the output be different? Or perhaps you are thinking about timing, when debugging, e.g. stopping at a breakpoint when the output have been buffered but not flushed to the terminal yet?