Skip to content
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

Suppress 7z x output in stack setup on Windows (WAS: stack --verbosity=error setup on Windows) #1991

Closed
hdgarrood opened this issue Apr 4, 2016 · 4 comments

Comments

@hdgarrood
Copy link

I am trying to set up Windows CI for purescript via appveyor, and I noticed that stack setup prints a massive amount of information which I don't really care about, at least, not when it succeeds. From reading the output of stack --help it appeared to me that using --verbosity=error would remove this output, but adding this option doesn't seem to have had any effect.

Here is the build: https://ci.appveyor.com/project/hdgarrood/purescript/build/13

@hdgarrood
Copy link
Author

Just to clarify: the command I'm using is stack --no-terminal --verbosity=error setup.

@mgsloan mgsloan added this to the P3: Optional milestone Apr 4, 2016
@borsboom
Copy link
Contributor

borsboom commented Apr 4, 2016

I think this is mostly the output of the GHC decompression being run as a subprocess, which stack's --verbosity doesn't effect. That said, there are probably ways we could suppress this output. The workaround I've seen people use is to run stack setup >nul (e.g. appveyor.yml).

@borsboom borsboom changed the title stack --verbosity=error setup on Windows Suppress 7z x output in stack setup on Windows (WAS: stack --verbosity=error setup on Windows) Apr 4, 2016
@hdgarrood
Copy link
Author

Yeah, I have something similar now, but simply suppressing the output is not quite what I'd consider ideal - if an error occurs during decompression, I do want to see it.

Currently I have stack setup --verbosity=error 2>&1 >stack-setup.log || type stack-setup.log which does seem to do what I want.

@sjakobi
Copy link
Member

sjakobi commented Jul 15, 2016

Closing as a duplicate of #1212.

@sjakobi sjakobi closed this as completed Jul 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants