-
Notifications
You must be signed in to change notification settings - Fork 132
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
"failed to decode PsaResult" when purs compile exits due to OOM #1284
Comments
Weird so we do catch non-ok exit cases |
Ah, it turns out we're not checking the exit status when trying to decode the compiler output in the psa machinery, see here: Lines 43 to 50 in b7c0483
In line 44 we call |
Spent several hours yesterday trying to figure out why my ci job running
spago build
/spago test
was failing despite nothing visibly changing in the environment, and thepurs compile
step exiting at random points in the build with:Eventually I had the thought "maybe the
--memory=1G
I added to the runner is makingpurs compile
exit early" which turned out to be exactly the case. Not sure if this is necessarily a bug in spago, just documenting this as an issue here for people who run into this in the future.The text was updated successfully, but these errors were encountered: