-
Notifications
You must be signed in to change notification settings - Fork 843
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'stack test' not referentially transparent #525
Comments
Please see https://github.com/commercialhaskell/stack/blob/master/CONTRIBUTING.md for guidelines on proper bug reporting format, which will make it possible to diagnose this efficiently. In particular, please:
|
Minimal steps:
Observe:
Run the command again:
This produces this output:
If you keep running Make this trivial change: diff --git a/spec/Spec.hs b/spec/Spec.hs
index c824a4c..934967b 100644
--- a/spec/Spec.hs
+++ b/spec/Spec.hs
@@ -1,4 +1,5 @@
{-# LANGUAGE OverloadedLists #-}
+
{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE Trustworthy #-} Run:
Observe compiler-error output from before:
I guess this is an issue of referential transparency. Apologies, I should know how to write a good bug report by now =p |
Can you check master and see if that resolves it? |
That appears to have fixed it! Thank you, @snoyberg! |
Thank you. That bug has popped in and out of existence multiple times, I'm On Mon, Jul 6, 2015, 9:30 AM Peter Harpending notifications@github.com
|
@(: :0:0) This looks familiar. I presume this indicates some sort of error that On Monday, July 6, 2015, Peter Harpending notifications@github.com wrote:
-- Dan Burton |
Edit: By the way, I have the latest git version of stack, as of 8:50 AM MDT, 2015-07-06.
Full tree: https://github.com/pharpend/comarkdown.
Here is my lovely test suite, with some compiler errors:
If I try to pipe the result of
stack test
to a pastebin, this is what shows up on the pastebin:That is, the output of the last successfully built test suite.
If I don't change the test suite, and try to run
stack test
again, I get the same output.However, before attempting to pipe the output of
stack test
to a pastebin, the output was this:If I make a trivial change to the test suite, and run
stack test
again, I get the compiler-errors output.The text was updated successfully, but these errors were encountered: