The forced buffering of output is a pain

[nikita-volkov]

Currently when I run a test suite I get a message like Test suite internal-tests: RUNNING... and no output of the traced messages or logging until the test-suite finishes, and even then, if it finishes with success, the only way to see the output is by viewing the log files.

Besides the fact that there's not much useful about such behaviour by itself and the pain it causes during debugging, when I need to see the output, it also causes troubles like inducing prolonged execution times for applications with much output. The last point is also a cause of another problem: the Travis CI terminates jobs that produce no output for 10 minutes.

As a reference here is a build, that suffers from the mentioned issues. The source code is linked from there.

To resolve the issue I suggest to disable such behaviour of HTF, or make it optional at least.

[skogsbaer]

This is not a problem of HTF but of cabal.

[nikita-volkov]

Oh. Sorry.

[nikita-volkov]

FI. Turns out, the issue is already reported there: haskell/cabal#1810.