-
Notifications
You must be signed in to change notification settings - Fork 703
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
cabal-install appears to hide stderr output on failure #7727
Comments
Related to #5974 and tickets mentioned there. So, probably an old problem. |
ulysses4ever
added a commit
to ulysses4ever/cabal
that referenced
this issue
Jul 18, 2022
3 tasks
ulysses4ever
added a commit
to ulysses4ever/cabal
that referenced
this issue
Jul 18, 2022
ulysses4ever
added a commit
that referenced
this issue
Oct 3, 2022
ulysses4ever
added a commit
to ulysses4ever/cabal
that referenced
this issue
Oct 7, 2022
Should be closed by #8296. Please, let us know if it doesn't. |
alexbiehl
pushed a commit
to alexbiehl/cabal
that referenced
this issue
Dec 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When investigating the failure of the
cabal-install-3.6
release CI pipeline on ARMv7, I noticed thatcabal-install
eats useful output from GHC upon failure. Specifically, the CI log ends with:What went wrong? It's not at all clear from this error and if I didn't happen to stumble upon the fact that code 251 is GHC's exit code on heap overflow I wouldn't have known myself.
Looking at
$CABAL_DIR/logs/ghc-8.10.7/Cabal-3.6.2.0-aa3b9fb077a93a7005de5308fb10da5d3f4036f77770639c1dad2871dc1f6799.log
removes any doubt:This output should have been reported to the user.
To Reproduce
Steps to reproduce the behavior:
Run a build that fails. Observe that the error is less than helpful
Expected behavior
The error output from GHC is passed on to the user.
System information
cabal-install-3.4.0.0
,ghc-8.10.7
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: