gatsby: CircleCI build Error: spawn ENOMEM

Description

CircleCI builds failed with the following error:

  Error: spawn ENOMEM
  
  - child_process.js:372 ChildProcess.spawn
    internal/child_process.js:372:11
  
  - worker.js:80 exports.default._initialize
    [src]/[jest-worker]/build/worker.js:80:69
  
  - worker.js:206 exports.default._exit
    [src]/[jest-worker]/build/worker.js:206:12
  
  - child_process.js:254 Process.ChildProcess._handle.onexit
    internal/child_process.js:254:12

Steps to reproduce

Slightly modify f74d723f037ca55068b456dc808ee3dd8ec563cc and send new pull request.

Expected result

Gatsby build should pass

Actual result

Build is not passing

Environment

System: OS: Linux 4.15 Debian GNU/Linux 9 (stretch) 9 (stretch) CPU: (36) x64 Intel® Xeon® Platinum 8124M CPU @ 3.00GHz Shell: 4.4.12 - /bin/bash Binaries: Node: 11.5.0 - /usr/local/bin/node Yarn: 1.12.3 - /usr/local/bin/yarn npm: 6.4.1 - /usr/local/bin/npm Languages: Python: 2.7.13 - /usr/bin/python npmPackages: gatsby: ^2.3.31 => 2.3.31 gatsby-image: ^2.0.37 => 2.0.37 gatsby-paginate: ^1.0.17 => 1.0.17 gatsby-plugin-catch-links: ^2.0.13 => 2.0.13 gatsby-plugin-favicon: ^3.1.6 => 3.1.6 gatsby-plugin-google-tagmanager: ^2.0.12 => 2.0.12 gatsby-plugin-manifest: ^2.0.26 => 2.0.26 gatsby-plugin-netlify: ^2.0.16 => 2.0.16 gatsby-plugin-offline: ^2.1.0 => 2.1.0 gatsby-plugin-react-helmet: ^3.0.12 => 3.0.12 gatsby-plugin-sentry: ^1.0.1 => 1.0.1 gatsby-plugin-sharp: ^2.0.32 => 2.0.32 gatsby-plugin-sitemap: ^2.0.11 => 2.0.11 gatsby-plugin-typography: ^2.2.10 => 2.2.10 gatsby-remark-images: ^3.0.10 => 3.0.10 gatsby-remark-prismjs: ^3.2.7 => 3.2.7 gatsby-source-filesystem: ^2.0.28 => 2.0.28 gatsby-transformer-json: ^2.1.11 => 2.1.11 gatsby-transformer-remark: ^2.3.8 => 2.3.8 gatsby-transformer-sharp: ^2.1.17 => 2.1.17

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 18 (4 by maintainers)

Most upvoted comments

same issue for me

Just a heads-up. We had the same issue here today and in our case we had a few images larger than 4000px and resizing them to 1920px solved the issue without having to touch circle config.

In our case setting env variable GATSBY_CPU_COUNT=1 helped (running gatsby@2.19.22)

Later we increased circle.ci resource_class to xlarge which solved ths issue. Apparently 4GB of RAM is not enough. Beware the resource_class feature might not be allowed in your plan, find out in your profile or contact circle.ci support.