You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building stack took lots of memory in other situations. Can anything be done to improve the situation? (I'd be open to workarounds on the stack/Travis side).
-- While building package store-0.4.1 using:
/home/travis/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_1.22.5.0_ghc-7.10.3 --builddir=.stack-work/dist/x86_64-linux/Cabal-1.22.5.0 build --ghc-options " -ddump-hi -ddump-to-file"
Process exited with code: ExitFailure (-9) (THIS MAY INDICATE OUT OF MEMORY)
Logs have been written to: /home/travis/build/commercialhaskell/stack/.stack-work/logs/store-0.4.1.log
This one fails on this file:
[ 9 of 11] Compiling Data.Store.Streaming ( src/Data/Store/Streaming.hs, .stack-work/dist/x86_64-linux/Cabal-1.22.5.0/build/Data/Store/Streaming.o )
The text was updated successfully, but these errors were encountered:
In the past few days I've noticed a few failures like the following, mentioning OOM
https://travis-ci.org/commercialhaskell/stack/jobs/234558520#L321-L324 (https://travis-ci.org/commercialhaskell/stack/jobs/234737983 was also one, but I had to restart it).
Building stack took lots of memory in other situations. Can anything be done to improve the situation? (I'd be open to workarounds on the stack/Travis side).
This one fails on this file:
The text was updated successfully, but these errors were encountered: