Every other build endsup with an error
Unanswered
Oriental posted this in #help-forum
OrientalOP
Something must have changed because every second build now ends up with:
"Error: Sandbox exited with unexpected code: {"code":1,"signal":null}"
Upon inspection we get this error:
"Error: The service is no longer running: write EPIPE"
Which seems to be related OOM error.
"Error: Sandbox exited with unexpected code: {"code":1,"signal":null}"
Upon inspection we get this error:
"Error: The service is no longer running: write EPIPE"
Which seems to be related OOM error.
7 Replies
OrientalOP
Here is more information.
This has been happening for the past couple of days.
We are building everything in GitHub and pushing to vercel just for the final deployment. Unfortunately there is no way to skip that final step. Previously the build system was completely unreliable and now with this it seems that there are new set of constraints to deploy effectively on your platform.
Bizarely every other build fails. In other words, if we rerun the job, it will succeed on the second time.
But it feels that this is so wasteful.
Not only waste build and deploy time on GitHub but it wastes resources on Vercel too.
This maybe a vercel issue.
I would recommend contacting Vercel customer support.
#vercel-help for more info
I would recommend contacting Vercel customer support.
#vercel-help for more info