Problem with stdout/stderr when using "jobs: $ncpus" configuration option #1554

Open
pmlodawski opened this Issue Oct 21, 2013 · 5 comments

Comments

Projects
None yet
7 participants

When enabled "jobs: $ncpus" configuration option, cabal prints errors to stdout instead of stderr.

@ghost ghost assigned 23Skidoo Oct 21, 2013

23Skidoo added a commit to 23Skidoo/cabal that referenced this issue Dec 7, 2013

23Skidoo added a commit to 23Skidoo/cabal that referenced this issue Dec 11, 2013

23Skidoo added a commit to 23Skidoo/cabal that referenced this issue Dec 17, 2013

23Skidoo added a commit to 23Skidoo/cabal that referenced this issue Dec 17, 2013

23Skidoo added a commit to 23Skidoo/cabal that referenced this issue Dec 17, 2013

23Skidoo added a commit to 23Skidoo/cabal that referenced this issue Dec 19, 2013

@23Skidoo 23Skidoo closed this in #1607 Dec 19, 2013

Member

23Skidoo commented Dec 20, 2013

Oops, wrong ticket reference.

@23Skidoo 23Skidoo reopened this Dec 20, 2013

jrm8005 commented Jan 22, 2014

I'm not sure if this is related, but apparently when setting jobs to either a number or $ncpus in the config file, cabal install no longer prints messages about what it is currently compiling, like "[n of m] Compiling Module.Foo ( src/Module/Foo.hs, dist/build/Module/Foo.o)", only running cabal build by hand does this.

Owner

tibbe commented Jan 22, 2014

This is by design, to reduce the amount of noise in the output. Cabal will
still errors. It would be useful to have some sort of per-package progress
indicator, but no one has implemented one.

On Wed, Jan 22, 2014 at 8:01 AM, jrm8005 notifications@github.com wrote:

I'm not sure if this is related, but apparently when setting jobs to
either a number or $ncpus in the config file, cabal install no longer
prints messages about what it is currently compiling, like "[n of m]
Compiling Module.Foo ( src/Module/Foo.hs, dist/build/Module/Foo.o)", only
running cabal build by hand does this.


Reply to this email directly or view it on GitHubhttps://github.com/haskell/cabal/issues/1554#issuecomment-33036734
.

Contributor

asr commented Jul 3, 2014

it would be useful to have some sort of per-package progress indicator

This information is useful when I'm building some programs such as Agda.

Contributor

asr commented Jul 3, 2014

I realised the issue reported and @jrm8005's comment are different. Should I open a new issue related to this comment?

@ttuegel ttuegel modified the milestones: cabal-install-1.24, cabal-install-1.22 Apr 23, 2015

@ttuegel ttuegel added the type: bug label Apr 23, 2015

@23Skidoo 23Skidoo modified the milestones: cabal-install 1.24, cabal-install 1.26 Feb 21, 2016

@23Skidoo 23Skidoo removed their assignment Jul 27, 2016

@ezyang ezyang modified the milestone: cabal-install 2.0 Sep 6, 2016

@zilinc zilinc referenced this issue in haskell-hvr/multi-ghc-travis Mar 21, 2017

Closed

commenting out jobs in cabal.config results in super slowdown #74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment