Failed during stage 'building site' since 02/01/2023

Hello,

I’m using Nuxt 2 with Nuxt generate.
Deployment used to work since 3 years on Netlify.
But it’s not working anymore since 1st february (with same commit allready worked). Does anything changed on that date ?

Thanks for your help and sorry for my english…

(build.command completed in 25m 19.3s)
8:12:28 AM: ​
8:12:28 AM: 2. Deploy site
8:12:28 AM: ────────────────────────────────────────────────────────────────
8:12:28 AM: ​
8:12:29 AM: Starting to deploy site from ‘dist’
8:12:29 AM: Calculating files to upload
8:12:31 AM: 5 new files to upload
8:12:31 AM: 0 new functions to upload
8:12:32 AM: Section completed: deploying
8:12:32 AM: Site deploy was successfully initiated
8:12:32 AM: ​
8:12:32 AM: (Deploy site completed in 3s)
8:12:32 AM: ​
8:12:32 AM: Netlify Build Complete
8:12:32 AM: ────────────────────────────────────────────────────────────────
8:12:32 AM: Starting post processing
8:12:32 AM: ​
8:12:32 AM: (Netlify Build completed in 25m 22.4s)
8:12:32 AM: Execution timed out after 32m44.875029236s
8:12:32 AM: Failed during stage ‘building site’: Command did not finish within the time limit
8:12:32 AM: Error running command: Command did not finish within the time limit
8:12:32 AM: Failing build: Failed to build site
8:12:32 AM: Skipping HTML post processing
8:12:32 AM: Finished processing build request in 32m50s

Hi @gregoirepuget :wave:t6: ,

Thanks so much for reaching out and welcome to the forums! It might be worth retrying with a cleared build cache first to see if that helps. If not check your building settings; Under the section Build Settings, Select Edit settings.

  • Change the build command as CI= npm run build

If that still doesn’t work can you please share the name of your site/slug?

Thanks for your help.

I would like to use nuxt generate and CI= npm run generate doesn’t work…

I also cleared build cache but not working better.

I’m still searching a solution.

The error is here. Do you mind letting us know the site name?

Hello,
Project is naughty-kilby-09f968.
website is admissions.fr
thank you

hi @gregoirepuget

thank you for sharing this. I noticed you’re using this command:

10:36:28 PM: > nuxt generate --quiet

Which makes it hard to understand why the build times-out. Mind changing that to be more verbose?

I can confirm what my colleague Hrishikesh pointed out of the build hitting the default time limit.

ok i removed quiet mode.

Mind sharing the output for that?

5:31:15 PM: build-image version: 01daab3416c9da7032f1dcdb8b1adffdaf5ccb74 (focal)
5:31:15 PM: buildbot version: 01daab3416c9da7032f1dcdb8b1adffdaf5ccb74
5:31:15 PM: Fetching cached dependencies
5:31:15 PM: Failed to fetch cache, continuing with build
5:31:15 PM: Starting to prepare the repo for build
5:31:16 PM: No cached dependencies found. Cloning fresh repo
5:31:16 PM: git clone --filter=blob:none git@gitlab.com:36pixels/projets/2020/admissions/admissions-front
5:31:17 PM: Preparing Git Reference refs/heads/master
5:31:19 PM: Parsing package.json dependencies
5:31:20 PM: Starting build script
5:31:20 PM: Installing dependencies
5:31:20 PM: Python version set to 2.7
5:31:20 PM: Attempting Node.js version 'v14.18.3' from .nvmrc
5:31:21 PM: Downloading and installing node v14.18.3...
5:31:21 PM: Downloading https://nodejs.org/dist/v14.18.3/node-v14.18.3-linux-x64.tar.xz...
5:31:21 PM: Computing checksum with sha256sum
5:31:21 PM: Checksums matched!
5:31:23 PM: Now using node v14.18.3 (npm v6.14.15)
5:31:23 PM: Started restoring cached build plugins
5:31:23 PM: Finished restoring cached build plugins
5:31:23 PM: Attempting Ruby version 2.7.1, read from environment
5:31:24 PM: Required ruby-2.7.1 is not installed - installing.
5:31:24 PM: Searching for binary rubies, this might take some time.
5:31:24 PM: Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/20.04/x86_64/ruby-2.7.1.tar.bz2
5:31:24 PM: Checking requirements for ubuntu.
5:31:24 PM: Requirements installation successful.
5:31:24 PM: ruby-2.7.1 - #configure
5:31:24 PM: ruby-2.7.1 - #download
5:31:25 PM: ruby-2.7.1 - #validate archive
5:31:28 PM: ruby-2.7.1 - #extract
5:31:30 PM: ruby-2.7.1 - #validate binary
5:31:31 PM: ruby-2.7.1 - #setup
5:31:31 PM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1@global
5:31:31 PM: ruby-2.7.1 - #importing gemset /opt/buildhome/.rvm/gemsets/global.gems........................................
5:31:31 PM: ruby-2.7.1 - #generating global wrappers........
5:31:31 PM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1
5:31:31 PM: ruby-2.7.1 - #importing gemsetfile /opt/buildhome/.rvm/gemsets/default.gems evaluated to empty gem list
5:31:32 PM: ruby-2.7.1 - #generating default wrappers........
5:31:32 PM: Using /opt/buildhome/.rvm/gems/ruby-2.7.1
5:31:32 PM: Using Ruby version 2.7.1
5:31:32 PM: Using PHP version 8.0
5:31:32 PM: Started restoring cached corepack dependencies
5:31:32 PM: Finished restoring cached corepack dependencies
5:31:33 PM: No npm workspaces detected
5:31:33 PM: Started restoring cached node modules
5:31:33 PM: Finished restoring cached node modules
5:31:33 PM: Installing npm packages using npm version 6.14.15
5:38:31 PM: npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
5:38:31 PM: > yorkie@2.0.0 install /opt/build/repo/node_modules/yorkie
5:38:31 PM: > node bin/install.js
5:38:31 PM: CI detected, skipping Git hooks installation
5:38:31 PM: > node-sass@4.14.1 install /opt/build/repo/node_modules/node-sass
5:38:31 PM: > node scripts/install.js
5:38:31 PM: Downloading binary from https://github.com/sass/node-sass/releases/download/v4.14.1/linux-x64-83_binding.node
5:38:31 PM: Download complete
5:38:31 PM: Binary saved to /opt/build/repo/node_modules/node-sass/vendor/linux-x64-83/binding.node
5:38:31 PM: Caching binary to /opt/buildhome/.npm/node-sass/4.14.1/linux-x64-83_binding.node
5:38:31 PM: > core-js@3.22.8 postinstall /opt/build/repo/node_modules/@vue/babel-preset-app/node_modules/core-js
5:38:31 PM: > node -e "try{require('./postinstall')}catch(e){}"
5:38:32 PM: > core-js@2.6.12 postinstall /opt/build/repo/node_modules/core-js
5:38:32 PM: > node -e "try{require('./postinstall')}catch(e){}"
5:38:32 PM: > core-js-pure@3.22.8 postinstall /opt/build/repo/node_modules/core-js-pure
5:38:32 PM: > node -e "try{require('./postinstall')}catch(e){}"
5:38:32 PM: > ejs@2.7.4 postinstall /opt/build/repo/node_modules/ejs
5:38:32 PM: > node ./postinstall.js
5:38:32 PM: > node-sass@4.14.1 postinstall /opt/build/repo/node_modules/node-sass
5:38:32 PM: > node scripts/build.js
5:38:32 PM: Binary found at /opt/build/repo/node_modules/node-sass/vendor/linux-x64-83/binding.node
5:38:32 PM: Testing binary
5:38:33 PM: Binary is fine
5:38:33 PM: > nuxt@2.12.2 postinstall /opt/build/repo/node_modules/nuxt
5:38:33 PM: > opencollective || exit 0
5:38:34 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
5:38:34 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
5:38:34 PM: added 2306 packages from 1106 contributors and audited 2333 packages in 420.948s
5:38:35 PM: 176 packages are looking for funding
5:38:35 PM:   run `npm fund` for details
5:38:35 PM: found 209 vulnerabilities (11 low, 11 moderate, 144 high, 43 critical)
5:38:35 PM:   run `npm audit fix` to fix them, or `npm audit` for details
5:38:35 PM: npm packages installed
5:38:35 PM: Started restoring cached go cache
5:38:35 PM: Finished restoring cached go cache
5:38:35 PM: Installing Go version 1.14.4 (requested 1.14.4)
5:38:41 PM: go version go1.14.4 linux/amd64
5:38:41 PM: Detected 2 framework(s)
5:38:41 PM: "nuxt" at version "2.12.2"
5:38:41 PM: "vue" at version "4.5.17"
5:38:41 PM: Installing missing commands
5:38:41 PM: Verify run directory
5:38:41 PM: Section completed: initializing
5:38:43 PM: ​
5:38:43 PM:   Netlify Build                                                 
5:38:43 PM: ────────────────────────────────────────────────────────────────
5:38:43 PM: ​
5:38:43 PM: ❯ Version
5:38:43 PM:   @netlify/build 29.5.4
5:38:43 PM: ​
5:38:43 PM: ❯ Flags
5:38:43 PM:   baseRelDir: true
5:38:43 PM:   buildId: 63ea65d2edd1200073847bd9
5:38:43 PM:   deployId: 63ea65d2dfe6060008f76a22
5:38:43 PM: ​
5:38:43 PM: ❯ Current directory
5:38:43 PM:   /opt/build/repo
5:38:43 PM: ​
5:38:43 PM: ❯ Config file
5:38:43 PM:   /opt/build/repo/netlify.toml
5:38:43 PM: ​
5:38:43 PM: ❯ Context
5:38:43 PM:   production
5:38:43 PM: ​
5:38:43 PM:   1. Build command from Netlify app                             
5:38:43 PM: ────────────────────────────────────────────────────────────────
5:38:43 PM: ​
5:38:43 PM: $ CI= npm run generate
5:38:43 PM: > starter@1.0.0 generate /opt/build/repo
5:38:43 PM: > nuxt generate
5:39:00 PM:  ERROR  [BABEL] Note: The code generator has deoptimised the styling of /opt/build/repo/components/section/simulation/form/FormSend.vue as it exceeds the max of 500KB.
5:39:00 PM:  ERROR  [BABEL] Note: The code generator has deoptimised the styling of /opt/build/repo/components/section/simulation/form/FormSendCommercial.vue as it exceeds the max of 500KB.
5:39:39 PM:  ERROR  [BABEL] Note: The code generator has deoptimised the styling of /opt/build/repo/components/section/simulation/form/FormSendCommercial.vue as it exceeds the max of 500KB.
5:39:39 PM:  ERROR  [BABEL] Note: The code generator has deoptimised the styling of /opt/build/repo/components/section/simulation/form/FormSend.vue as it exceeds the max of 500KB.
6:04:11 PM: ​
6:04:11 PM: (build.command completed in 25m 28.1s)
6:04:11 PM: ​
6:04:11 PM:   2. Deploy site                                                
6:04:11 PM: ────────────────────────────────────────────────────────────────
6:04:11 PM: ​
6:04:11 PM: Starting to deploy site from 'dist'
6:04:12 PM: Calculating files to upload
6:04:14 PM: 6 new files to upload
6:04:14 PM: 0 new functions to upload
6:04:14 PM: Section completed: deploying
6:04:14 PM: Site deploy was successfully initiated
6:04:14 PM: ​
6:04:14 PM: (Deploy site completed in 3s)
6:04:14 PM: ​
6:04:14 PM:   Netlify Build Complete                                        
6:04:14 PM: ────────────────────────────────────────────────────────────────
6:04:14 PM: ​
6:04:14 PM: Starting post processing
6:04:14 PM: (Netlify Build completed in 25m 31.2s)
6:04:14 PM: Execution timed out after 32m54.155154148s
6:04:14 PM: Error running command: Command did not finish within the time limit
6:04:14 PM: Failing build: Failed to build site
6:04:14 PM: Failed during stage 'building site': Command did not finish within the time limit
6:04:14 PM: Skipping HTML post processing
6:04:15 PM: Finished processing build request in 32m59.266s
6:04:15 PM: Post processing - header rules
6:04:15 PM: Post processing - redirect rules

Hey @gregoirepuget,

Based on your site’s deploy history, this doesn’t seem to be a new problem. As far as I can see, except for the first deploy, all have got this error: Netlify App

It’s just that now the error is blocking the publishing, but you’ve always been hitting the time limits. Have you tried to build this in CLI or Netlify Docker image to see how long it takes?

That’s right but before 1st february, this error didn’t block the publishing.

We already use Netlify Docker and it takes about 10-12 min to build

I’d say you got lucky because it was a matter of race condition. It was supposed to stop working sooner or later, so now it did.

I have now pushed the limit to an hour so your build should work fine.