Deploy Keeps Failing

Support
1

Hello,

since yesterday I have been trying to update my site but it keeps failing although the local build runs perfectly fine! I didn’t change anything in the build settings or install any new packages or libraries, so I am not sure what is going on.

Netlify site name: loyacsystem

You will find attached a screenshot of my build settings, and here is my deploy log:

3:23:33 PM: Build ready to start
3:23:41 PM: build-image version: d7b3dbfb0846505993c9a131894d1858074c90b4 (focal)
3:23:41 PM: build-image tag: v4.10.1
3:23:41 PM: buildbot version: 4cffa5dc84445a450e8be6f710e2498d87994fae
3:23:41 PM: Fetching cached dependencies
3:23:41 PM: Starting to download cache of 401.8MB
3:23:45 PM: Finished downloading cache in 4.199495029s
3:23:45 PM: Starting to extract cache
3:23:52 PM: Finished extracting cache in 6.393518397s
3:23:52 PM: Finished fetching cache in 10.674899649s
3:23:52 PM: Starting to prepare the repo for build
3:23:52 PM: Preparing Git Reference refs/heads/master
3:23:53 PM: Parsing package.json dependencies
3:23:54 PM: Starting build script
3:23:54 PM: Installing dependencies
3:23:54 PM: Python version set to 2.7
3:23:54 PM: Started restoring cached node version
3:23:54 PM: Finished restoring cached node version
3:23:55 PM: v14.15.0 is already installed.
3:23:55 PM: Now using node v14.15.0 (npm v6.14.8)
3:23:55 PM: Started restoring cached build plugins
3:23:55 PM: Finished restoring cached build plugins
3:23:55 PM: Attempting ruby version 2.7.2, read from environment
3:23:55 PM: Using ruby version 2.7.2
3:23:56 PM: Using PHP version 8.0
3:23:56 PM: Started restoring cached yarn cache
3:23:59 PM: Finished restoring cached yarn cache
3:24:00 PM: No yarn workspaces detected
3:24:00 PM: Started restoring cached node modules
3:24:00 PM: Finished restoring cached node modules
3:24:00 PM: Installing NPM modules using Yarn version 1.22.10
3:24:00 PM: yarn install v1.22.10
3:24:00 PM: [1/4] Resolving packages...
3:24:00 PM: [2/4] Fetching packages...
3:24:11 PM: info fsevents@2.1.2: The platform "linux" is incompatible with this module.
3:24:11 PM: info "fsevents@2.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
3:24:11 PM: info fsevents@1.2.13: The platform "linux" is incompatible with this module.
3:24:11 PM: info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
3:24:11 PM: info fsevents@2.3.2: The platform "linux" is incompatible with this module.
3:24:11 PM: info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
3:24:11 PM: [3/4] Linking dependencies...
3:24:11 PM: warning "@react-pdf/renderer > react-reconciler@0.24.0" has incorrect peer dependency "react@^16.0.0".
3:24:11 PM: warning " > bootstrap@4.6.2" has unmet peer dependency "jquery@1.9.1 - 3".
3:24:11 PM: warning " > bootstrap@4.6.2" has unmet peer dependency "popper.js@^1.16.1".
3:24:11 PM: warning " > react-block-ui@1.3.3" has incorrect peer dependency "react@^0.14.9 || ^15.3.0 || ^16.0.0".
3:24:11 PM: warning " > react-block-ui@1.3.3" has incorrect peer dependency "react-dom@^0.14.9 || ^15.3.0 || ^16.0.0".
3:24:11 PM: warning " > react-fixed-sidebar@1.1.3" has incorrect peer dependency "react@^15.0.1".
3:24:11 PM: warning "react-scripts > @typescript-eslint/eslint-plugin > tsutils@3.21.0" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
3:24:11 PM: warning " > styled-components@5.3.5" has unmet peer dependency "react-is@>= 16.8.0".
3:24:18 PM: [4/4] Building fresh packages...
3:24:19 PM: Done in 19.24s.
3:24:19 PM: NPM modules installed using Yarn
3:24:19 PM: Started restoring cached go cache
3:24:19 PM: Finished restoring cached go cache
3:24:19 PM: Installing Go version 1.17 (requested 1.17)
3:24:24 PM: unset GOOS;
3:24:24 PM: unset GOARCH;
3:24:24 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.17.linux.amd64';
3:24:24 PM: export PATH="/opt/buildhome/.gimme/versions/go1.17.linux.amd64/bin:${PATH}";
3:24:24 PM: go version >&2;
3:24:24 PM: export GIMME_ENV="/opt/buildhome/.gimme/env/go1.17.linux.amd64.env"
3:24:24 PM: go version go1.17 linux/amd64
3:24:24 PM: Installing missing commands
3:24:24 PM: Verify run directory
3:24:25 PM: ​
3:24:25 PM: ────────────────────────────────────────────────────────────────
3:24:25 PM:   Netlify Build                                                 
3:24:25 PM: ────────────────────────────────────────────────────────────────
3:24:25 PM: ​
3:24:25 PM: ❯ Version
3:24:25 PM:   @netlify/build 27.11.5
3:24:25 PM: ​
3:24:25 PM: ❯ Flags
3:24:25 PM:   baseRelDir: true
3:24:25 PM:   buildId: 62fe2f451573f4000927d7bd
3:24:25 PM:   deployId: 62fe2f451573f4000927d7bf
3:24:25 PM: ​
3:24:25 PM: ❯ Current directory
3:24:25 PM:   /opt/build/repo
3:24:25 PM: ​
3:24:25 PM: ❯ Config file
3:24:25 PM:   /opt/build/repo/netlify.toml
3:24:25 PM: ​
3:24:25 PM: ❯ Context
3:24:25 PM:   production
3:24:25 PM: ​
3:24:25 PM: ────────────────────────────────────────────────────────────────
3:24:25 PM:   1. Build command from Netlify app                             
3:24:25 PM: ────────────────────────────────────────────────────────────────
3:24:25 PM: ​
3:24:25 PM: $ yarn build
3:24:25 PM: yarn run v1.22.10
3:24:25 PM: $ react-scripts build
3:24:25 PM: Creating an optimized production build...
3:25:40 PM: <--- Last few GCs --->
3:25:40 PM: [1478:0x63729f0]    74943 ms: Scavenge (reduce) 1951.5 (2053.3) -> 1951.4 (2054.6) MB, 1.8 / 0.0 ms  (average mu = 0.921, current mu = 0.949) allocation failure
3:25:40 PM: [1478:0x63729f0]    74946 ms: Scavenge (reduce) 1952.6 (2047.8) -> 1952.5 (2051.1) MB, 1.7 / 0.0 ms  (average mu = 0.921, current mu = 0.949) allocation failure
3:25:40 PM: [1478:0x63729f0]    74950 ms: Scavenge (reduce) 1953.5 (2055.6) -> 1953.4 (2056.8) MB, 1.8 / 0.0 ms  (average mu = 0.921, current mu = 0.949) allocation failure
3:25:40 PM: <--- JS stacktrace --->
3:25:40 PM: FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory
3:25:40 PM:  1: 0xa03530 node::Abort() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM:  2: 0x94e471 node::FatalError(char const*, char const*) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM:  3: 0xb7773e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM:  4: 0xb77ab7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM:  5: 0xd32345  [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM:  6: 0xd62ede v8::internal::EvacuateNewSpaceVisitor::Visit(v8::internal::HeapObject, int) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM:  7: 0xd6ef16 v8::internal::FullEvacuator::RawEvacuatePage(v8::internal::MemoryChunk*, long*) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM:  8: 0xd5b0ff v8::internal::Evacuator::EvacuatePage(v8::internal::MemoryChunk*) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM:  9: 0xd5b378 v8::internal::PageEvacuationTask::RunInParallel(v8::internal::ItemParallelJob::Task::Runner) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 10: 0xd4dc59 v8::internal::ItemParallelJob::Run() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 11: 0xd70e70 void v8::internal::MarkCompactCollectorBase::CreateAndExecuteEvacuationTasks<v8::internal::FullEvacuator, v8::internal::MarkCompactCollector>(v8::internal::MarkCompactCollector*, v8::internal::ItemParallelJob*, v8::internal::MigrationObserver*, long) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 12: 0xd7170c v8::internal::MarkCompactCollector::EvacuatePagesInParallel() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 13: 0xd718d5 v8::internal::MarkCompactCollector::Evacuate() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 14: 0xd838c1 v8::internal::MarkCompactCollector::CollectGarbage() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 15: 0xd3fbe8 v8::internal::Heap::MarkCompact() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 16: 0xd416d8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 17: 0xd424a7 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 18: 0xd468a2 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 19: 0xc6a96b non-virtual thunk to v8::internal::CancelableTask::Run() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 20: 0xa71704 node::PerIsolatePlatformData::RunForegroundTask(std::unique_ptr<v8::Task, std::default_delete<v8::Task> >) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 21: 0xa73569 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 22: 0x1379a66  [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 23: 0x138c545  [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 24: 0x137a398 uv_run [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 25: 0xa438d4 node::NodeMainInstance::Run() [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 26: 0x9d1735 node::Start(int, char**) [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:40 PM: 27: 0x7fbfe3f94083 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
3:25:40 PM: 28: 0x96971c  [/opt/buildhome/.nvm/versions/node/v14.15.0/bin/node]
3:25:42 PM: error Command failed with exit code 1. (https://ntl.fyi/exit-code-1)
3:25:42 PM: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
3:25:42 PM: ​
3:25:42 PM: ────────────────────────────────────────────────────────────────
3:25:42 PM:   "build.command" failed                                        
3:25:42 PM: ────────────────────────────────────────────────────────────────
3:25:42 PM: ​
3:25:42 PM:   Error message
3:25:42 PM:   Command failed with exit code 1: yarn build (https://ntl.fyi/exit-code-1)
3:25:42 PM: ​
3:25:42 PM:   Error location
3:25:42 PM:   In Build command from Netlify app:
3:25:42 PM:   yarn build
3:25:42 PM: ​
3:25:42 PM:   Resolved config
3:25:42 PM:   build:
3:25:42 PM:     command: yarn build
3:25:42 PM:     commandOrigin: ui
3:25:42 PM:     environment:
3:25:42 PM:       - NODE_VERSION
3:25:42 PM:       - REACT_APP_BACKEND_DOMAIN
3:25:42 PM:       - REACT_APP_FRONTEND_DOMAIN
3:25:42 PM:     publish: /opt/build/repo/build
3:25:42 PM:     publishOrigin: ui
3:25:42 PM:   redirects:
3:25:43 PM:     - from: /*
      status: 200
      to: /index.html
  redirectsOrigin: config
Caching artifacts
3:25:43 PM: Started saving node modules
3:25:43 PM: Finished saving node modules
3:25:43 PM: Started saving build plugins
3:25:43 PM: Finished saving build plugins
3:25:43 PM: Started saving yarn cache
3:26:41 PM: Finished saving yarn cache
3:26:41 PM: Started saving pip cache
3:26:41 PM: Finished saving pip cache
3:26:41 PM: Started saving emacs cask dependencies
3:26:41 PM: Finished saving emacs cask dependencies
3:26:41 PM: Started saving maven dependencies
3:26:41 PM: Finished saving maven dependencies
3:26:41 PM: Started saving boot dependencies
3:26:41 PM: Finished saving boot dependencies
3:26:41 PM: Started saving rust rustup cache
3:26:41 PM: Finished saving rust rustup cache
3:26:41 PM: Started saving go dependencies
3:26:41 PM: Finished saving go dependencies
3:26:41 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
3:26:41 PM: Creating deploy upload records
3:26:41 PM: Failing build: Failed to build site
3:26:41 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
3:26:41 PM: Finished processing build request in 3m0.444148825s

build settings

2

Hi @LOYAC

The issue you are seeing is due to over allocation of memory as explained in the following support guide

3

Hi @coelmay

I added NODE_OPTIONS to my environment variables to solve the memory issue as you can see in the attached image, but still, the deployment is failing, I am getting the following and I am not sure if it is related to the over-allocation of memory or if it is a new issue?

1:04:39 PM: Build ready to start
1:04:41 PM: build-image version: d7b3dbfb0846505993c9a131894d1858074c90b4 (focal)
1:04:41 PM: build-image tag: v4.10.1
1:04:41 PM: buildbot version: 4cffa5dc84445a450e8be6f710e2498d87994fae
1:04:41 PM: Building without cache
1:04:41 PM: Starting to prepare the repo for build
1:04:41 PM: No cached dependencies found. Cloning fresh repo
1:04:41 PM: git clone https://github.com/LOYAC/Operation-Cobra---Frontend
1:04:43 PM: Preparing Git Reference refs/heads/master
1:04:43 PM: Parsing package.json dependencies
1:04:44 PM: Starting build script
1:04:44 PM: Installing dependencies
1:04:44 PM: Python version set to 2.7
1:04:45 PM: Downloading and installing node v16.15.0...
1:04:45 PM: Downloading https://nodejs.org/dist/v16.15.0/node-v16.15.0-linux-x64.tar.xz...
1:04:45 PM: Computing checksum with sha256sum
1:04:45 PM: Checksums matched!
1:04:47 PM: Now using node v16.15.0 (npm v8.5.5)
1:04:47 PM: Started restoring cached build plugins
1:04:47 PM: Finished restoring cached build plugins
1:04:47 PM: Attempting ruby version 2.7.2, read from environment
1:04:48 PM: Using ruby version 2.7.2
1:04:48 PM: Using PHP version 8.0
1:04:48 PM: Started restoring cached yarn cache
1:04:48 PM: Finished restoring cached yarn cache
1:04:48 PM: No yarn workspaces detected
1:04:48 PM: Started restoring cached node modules
1:04:48 PM: Finished restoring cached node modules
1:04:48 PM: Installing NPM modules using Yarn version 1.22.10
1:04:49 PM: yarn install v1.22.10
1:04:49 PM: [1/4] Resolving packages...
1:04:49 PM: [2/4] Fetching packages...
1:05:05 PM: info fsevents@2.1.2: The platform "linux" is incompatible with this module.
1:05:05 PM: info "fsevents@2.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
1:05:05 PM: info fsevents@1.2.13: The platform "linux" is incompatible with this module.
1:05:05 PM: info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
1:05:05 PM: info fsevents@2.3.2: The platform "linux" is incompatible with this module.
1:05:05 PM: info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
1:05:05 PM: [3/4] Linking dependencies...
1:05:05 PM: warning "@react-pdf/renderer > react-reconciler@0.24.0" has incorrect peer dependency "react@^16.0.0".
1:05:05 PM: warning " > bootstrap@4.6.2" has unmet peer dependency "jquery@1.9.1 - 3".
1:05:05 PM: warning " > bootstrap@4.6.2" has unmet peer dependency "popper.js@^1.16.1".
1:05:05 PM: warning " > react-block-ui@1.3.3" has incorrect peer dependency "react@^0.14.9 || ^15.3.0 || ^16.0.0".
1:05:05 PM: warning " > react-block-ui@1.3.3" has incorrect peer dependency "react-dom@^0.14.9 || ^15.3.0 || ^16.0.0".
1:05:05 PM: warning " > react-fixed-sidebar@1.1.3" has incorrect peer dependency "react@^15.0.1".
1:05:05 PM: warning "react-scripts > @typescript-eslint/eslint-plugin > tsutils@3.21.0" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
1:05:06 PM: warning " > styled-components@5.3.5" has unmet peer dependency "react-is@>= 16.8.0".
1:05:15 PM: [4/4] Building fresh packages...
1:05:16 PM: Done in 27.72s.
1:05:16 PM: NPM modules installed using Yarn
1:05:16 PM: Started restoring cached go cache
1:05:16 PM: Finished restoring cached go cache
1:05:16 PM: Installing Go version 1.17 (requested 1.17)
1:05:23 PM: unset GOOS;
1:05:23 PM: unset GOARCH;
1:05:23 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.17.linux.amd64';
1:05:23 PM: export PATH="/opt/buildhome/.gimme/versions/go1.17.linux.amd64/bin:${PATH}";
1:05:23 PM: go version >&2;
1:05:23 PM: export GIMME_ENV="/opt/buildhome/.gimme/env/go1.17.linux.amd64.env"
1:05:23 PM: go version go1.17 linux/amd64
1:05:23 PM: Installing missing commands
1:05:23 PM: Verify run directory
1:05:24 PM: ​
1:05:24 PM: ────────────────────────────────────────────────────────────────
1:05:24 PM:   Netlify Build                                                 
1:05:24 PM: ────────────────────────────────────────────────────────────────
1:05:24 PM: ​
1:05:24 PM: ❯ Version
1:05:24 PM:   @netlify/build 27.11.5
1:05:24 PM: ​
1:05:24 PM: ❯ Flags
1:05:24 PM:   baseRelDir: true
1:05:24 PM:   buildId: 62ff60376160006d77c2971a
1:05:24 PM:   deployId: 62ff60376160006d77c2971c
1:05:24 PM: ​
1:05:24 PM: ❯ Current directory
1:05:24 PM:   /opt/build/repo
1:05:24 PM: ​
1:05:24 PM: ❯ Config file
1:05:24 PM:   /opt/build/repo/netlify.toml
1:05:24 PM: ​
1:05:24 PM: ❯ Context
1:05:24 PM:   production
1:05:24 PM: ​
1:05:24 PM: ────────────────────────────────────────────────────────────────
1:05:24 PM:   1. Build command from Netlify app                             
1:05:24 PM: ────────────────────────────────────────────────────────────────
1:05:24 PM: ​
1:05:24 PM: $ yarn build
1:05:25 PM: yarn run v1.22.10
1:05:25 PM: $ react-scripts build
1:05:25 PM: Creating an optimized production build...
1:07:32 PM: The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.
1:07:32 PM: error Command failed with exit code 1. (https://ntl.fyi/exit-code-1)
1:07:32 PM: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
1:07:32 PM: ​
1:07:32 PM: ────────────────────────────────────────────────────────────────
1:07:32 PM:   "build.command" failed                                        
1:07:32 PM: ────────────────────────────────────────────────────────────────
1:07:32 PM: ​
1:07:32 PM:   Error message
1:07:32 PM:   Command failed with exit code 1: yarn build (https://ntl.fyi/exit-code-1)
1:07:32 PM: ​
1:07:32 PM:   Error location
1:07:32 PM:   In Build command from Netlify app:
1:07:32 PM:   yarn build
1:07:32 PM: ​
1:07:32 PM:   Resolved config
1:07:32 PM:   build:
1:07:32 PM:     command: yarn build
1:07:32 PM:     commandOrigin: ui
1:07:32 PM:     environment:
1:07:32 PM:       - NODE_OPTIONS
1:07:32 PM:       - NODE_VERSION
1:07:32 PM:       - REACT_APP_BACKEND_DOMAIN
1:07:32 PM:       - REACT_APP_FRONTEND_DOMAIN
1:07:32 PM:     publish: /opt/build/repo/build
1:07:32 PM:     publishOrigin: ui
1:07:32 PM:   redirects:
1:07:32 PM:     - from: /*      status: 200      to: /index.html  redirectsOrigin: configCaching artifacts
1:07:32 PM: Started saving node modules
1:07:32 PM: Finished saving node modules
1:07:32 PM: Started saving build plugins
1:07:32 PM: Finished saving build plugins
1:07:32 PM: Started saving yarn cache
1:08:09 PM: Finished saving yarn cache
1:08:09 PM: Started saving pip cache
1:08:09 PM: Finished saving pip cache
1:08:09 PM: Started saving emacs cask dependencies
1:08:09 PM: Finished saving emacs cask dependencies
1:08:09 PM: Started saving maven dependencies
1:08:09 PM: Finished saving maven dependencies
1:08:09 PM: Started saving boot dependencies
1:08:09 PM: Finished saving boot dependencies
1:08:09 PM: Started saving rust rustup cache
1:08:09 PM: Finished saving rust rustup cache
1:08:09 PM: Started saving go dependencies
1:08:09 PM: Finished saving go dependencies
1:08:12 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
1:08:12 PM: Creating deploy upload records
1:08:12 PM: Failing build: Failed to build site
1:08:12 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
1:08:12 PM: Finished processing build request in 3m31.25888934s

env var
env var840×196 13.1 KB

4

Your build is still running out of memory.

You may need to use Netlify CLI to build locally and deploy manually unless you can determine why the build is using so much memory and how to reduce it.

5

@coelmay

Okay, I will see what I can do.

Thanks for the help.