"stdout" test stalls temporarily sometimes

[chrismwendt]

"stdout" test stalls temporarily sometimes

[chrismwendt]

Workarounds/solutions:

• Specify a different hspec formatter that doesn't print to stdout while the test is running, but it's unintuitive for the test passing to depend on which test framework formatter you're using.
• The test could run in a subprocess so that it has a different stdout. That's a pretty heavyweight solution.
• Put the test behind a flag like --enable-stdout-tests and default to disabled.
• Always run stack test conduit | cat to trick hspec into disabling progress since it checks for NO_COLOR and a terminal

[snoyberg]

stdoutC is a thin wrapper around sinkHandle. It's probably best to simply skip this test and rely on tests of sinkHandle instead. I'd accept a PR for this. However, I've never experienced this behavior myself, and it may indicate that there are issues elsewhere. I don't think conduit is the culprit here.

[chrismwendt]

The timer ticks at 0.05s intervals, so slower machines are more likely to encounter the error (maybe yours is fast). It's moreso the conflicting uses of stdout between hspec and the conduit tests than one or the other individually that's causing this issue. PR: #480