Should this work? #947
Should this work? #947
Comments
For what it's worth, |
This isn't an issue with stack - the build for haskell-src-exts is running out of memory. See #859 |
Damnit, I was just a bit too slow to close this myself. Sorry about this. |
No problem! Thanks for reporting :) Better to over-report than under-report. However, it is good to search around for existing issues / explanations first, though. |
Can stack detect when the child process died with -9 and print a helpful message about how compilation ran out of memory? |
No, since the child process is Cabal the library, not GHC. Cabal would need On Tue, Sep 8, 2015, 5:56 AM Christopher Armstrong notifications@github.com
|
@snoyberg Okay, filed haskell/cabal#2813 - Thanks for the explanation. |
Looks good, thanks! On Tue, Sep 8, 2015 at 7:01 AM, Christopher Armstrong <
|
It looks to me like the |
How would this look? Just add a simple |
Is that necessary? The |
Wow, you're right, I can't believe I didn't see that. OK, my mistake. |
My 2 cents user feedback on that is that silent out-of-memory error are very frustrating. I experienced this several time when compiling some projects on various remote low-end machines. I am even used to start |
Actually, @mgsloan brought up something around auto-retrying a build due to memory exhaustion, and I made the same mistake of thinking we couldn't reliably detect it. Perhaps we should implement some logic along the lines of:
|
FWIW, signal 9 is just |
I should have noticed that... OK, I'm not convinced that what I described above is still a good idea, but it might be. After all, how common will it be that someone will |
As a starting point, I just pushed a change that switches the message to
|
Since we can't count on |
Brand new stack install on Debian. No GHC installed.
This is using lts-3.4
On the one hand, I'm not sure how I could have done things differently, but on the other,
haskell-src-exts
is used, or at least used to be used, by quite a few packages, and I can't find any reference of people running into this problem.Perhaps stackoverflow would have been a better place to post this. Apologies if so.
The text was updated successfully, but these errors were encountered: