Sitename: bonjoro-marketing.netlify.app I’m getting this error when building in netlify - I’m running the same command on my local and I don’t encounter the same issue. I feel like this could be related to timeout because we are building quite a few pages and because it was Killed (I’m not sure). …

@bonjoro-dev Are you able to provide the full build log? The section that you have screenshot doesn’t provide much context for seeing what may have triggered it. Have you checked the link that the error provides, which links to other discussions around that error code: Search results fo…

I can but I prefer to send it through email. Send me your email address. To what it’s worth, there’s no build error other than the code 137.

@bonjoro-dev I’m not Netlify staff but just a community member, if you can’t provide the details publicly that’s fine, you’ll just have to wait for Netlify support.

[image] bonjoro-dev: To what it’s worth, there’s no build error other than the code 137. While there may be no other build error than the 137, what’s frequently important with errors is “where they occur”, and “what the build was doing when they occurred”. For example if the build is process…

I’ve increased the node stack size, and now I’m getting a different error. @nathanmartin Here’s the full log https://gist.github.com/albertBuenaventura/c2ec9423544dc724ad0db9d4057ef313 netlify-error 9:05:15 PM: Build command from Netlify app 9:05:15 PM…

@bonjoro-dev Your build is throwing warnings, which will cause the build to fail unless CI is set to false. You can try adding CI= to your build command. cross-env NODE_OPTIONS='--max-old-space-size=8192' CI= next build

@nathanmartin I tried but didn’t worked. Adding CI= didn’t make any difference nor removing the warnings (I disabled the eslint warnings on build). Here’s the updated log. https://gist.github.com/albertBuenaventura/42822c29af90b25114004e612f8ff9ed netlify-error-2 10:09:19 AM: Build co…

It never removes the warnings, it just prevents them from causing the built to fail IF that is what is causing it to fail, (which it may not be - it’s just something I spotted which does commonly cause builds to fail).

@nathanmartin the issue is intermittent. It was able to run successfully once, but when I tried re-deploy again it fails. Could be running out of memory. Really frustrating.

@bonjoro-dev You certainly might be, here’s a Support Guide for memory usage: [image] [Support Guide] Making sure your builds use appropriate resources for Netlify's build system Support Guides updated in Dec 2022 Hopefully, your builds at Netlify “just work”, once you h…

Getting an error "Command failed with exit code 137: yarn run build" and it looks like just a timeout

Support

nathanmartin June 20, 2023, 3:38am 11

@bonjoro-dev You certainly might be, here’s a Support Guide for memory usage:

Topic		Replies	Views
Error Command failed with exit code 137. (https://ntl.fyi/exit-code-137) Support building , deployment	3	972	January 8, 2023
Build process killed 127 Support building , deployment	1	526	August 8, 2023
More build time Support building , gatsby , branch-deploys	1	1393	April 29, 2022
Buidling using NextJS command failed Support building	5	358	March 4, 2024
Command failed with exit code 137 Support building , nextjs	10	1878	June 22, 2023

Getting an error "Command failed with exit code 137: yarn run build" and it looks like just a timeout

Related topics