when working on some test specs and having stack rebuild and test on file modification, i observe some strange output that appears to come about due to the order of text output to the console.
the behaviour i note is output like the following
...
Compl[t3e1dmTest suite failure for package thing-0.1.0.0
thing-test: exited with: ExitFailure 1
Logs printed to console
2[a0cmtiToynp(es )h.e
lp for available commands. Press enter to force a rebuild.
(note that control characters have been interspersed amongst regular output)
my environment
06:10 PM noon ∈ >stack --version
Version 1.0.0, Git revision 3bc26237b5b3c387b8fd564459ea4dd88fd58b30 (2939 commits) x86_64
06:12 PM noon ∈ >uname -m && cat /etc/*release
x86_64
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
NAME="Ubuntu"
VERSION="14.04.2 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.2 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
to reproduce this bug,
stack new thing hspec (new project from the hspec template)stack build --file-watch --test build and watch for changes and run tests- make some change to one of the tests and make it fail
i just added to the existing spec
it "fails" $ do
True `shouldBe` False
now, i only observe this quirk when the tests fail, and when i actually make a change to the file itself, as opposed to just pressing enter in the stack terminal to re-build.
if it's relevant, i'm using zsh for my shell
06:12 PM noon ∈ >zsh --version
zsh 5.0.2 (x86_64-pc-linux-gnu)
(i'll note that it works fine if i press enter; with the failing output suitably coloured red; in an earlier version of stack i was using i got similar garbled text, but the output was no longer red when it failed. in this version, it's always red, but the final few lines are garbled.)
when working on some test specs and having stack rebuild and test on file modification, i observe some strange output that appears to come about due to the order of text output to the console.
the behaviour i note is output like the following
(note that control characters have been interspersed amongst regular output)
my environment
to reproduce this bug,
stack new thing hspec(new project from the hspec template)stack build --file-watch --testbuild and watch for changes and run testsi just added to the existing spec
now, i only observe this quirk when the tests fail, and when i actually make a change to the file itself, as opposed to just pressing enter in the stack terminal to re-build.
if it's relevant, i'm using
zshfor my shell(i'll note that it works fine if i press enter; with the failing output suitably coloured red; in an earlier version of stack i was using i got similar garbled text, but the output was no longer red when it failed. in this version, it's always red, but the final few lines are garbled.)