testsuite: Fix putStrLn in saks028

Authored by bgamari on Nov 7 2019, 9:29 AM.

Description

testsuite: Fix putStrLn in saks028

Bizarrely, saks028 previously failed reliably, but only on Windows
(Trac #17450). The test would exit with a zero exit code but simply didn't
emit the expected text to stderr.

I believe this was due to the fact that the test used putStrLn,
resulting in the output ending up on stdout. This worked on other
platforms since (apparently) we redirect stdout to stderr when
evaluating splices. However, on Windows it seems that the redirected
output wasn't flushed as it was on other platforms.

Anyways, it seems like the right thing to do here is to be explicit
about our desire for the output to end up on stderr.

Closes Trac #17450.

Details

Committed
Marge Bot <ben+marge-bot@smart-cactus.org>Nov 9 2019, 5:03 PM
Parents
rGHCf73fbd2dac42: testsuite: Ignore stderr in PartialDownsweep
Branches
Unknown
Tags
Unknown
Marge Bot <ben+marge-bot@smart-cactus.org> committed rGHCa9b147907b69: testsuite: Fix putStrLn in saks028 (authored by bgamari).Nov 9 2019, 5:03 PM