Building says it's built, wont go to deployment

[eewew]

Logs:
8:54:10 PM: Netlify Build
8:54:10 PM: ────────────────────────────────────────────────────────────────
8:54:10 PM: ​
8:54:10 PM: ❯ Version
8:54:10 PM: @netlify/build 33.5.0
8:54:10 PM: ​
8:54:10 PM: ❯ Flags
8:54:10 PM: accountId: 686742168a1903f5c5d24040
8:54:10 PM: baseRelDir: true
8:54:10 PM: buildId: 68674235f2dceee35daaf528
8:54:10 PM: deployId: 68674235f2dceee35daaf52a
8:54:11 PM: ​
8:54:11 PM: ❯ Current directory
8:54:11 PM: /opt/build/repo
8:54:11 PM: ​
8:54:11 PM: ❯ Config file
8:54:11 PM: /opt/build/repo/netlify.toml
8:54:11 PM: ​
8:54:11 PM: ❯ Context
8:54:11 PM: production
8:54:11 PM: ​
8:54:11 PM: build.command from netlify.toml
8:54:11 PM: ────────────────────────────────────────────────────────────────
8:54:11 PM: ​
8:54:11 PM: $ npm run build:client
8:54:11 PM: > build:client
8:54:11 PM: > vite build
8:54:12 PM: vite v6.3.5 building for production…
8:54:12 PM: transforming…
8:54:12 PM: Bot status monitor ready as Apex#5250
8:54:13 PM: Discord bot logged in as Apex#5250
8:54:16 PM: ✓ 1684 modules transformed.
8:54:16 PM: rendering chunks…
8:54:16 PM: computing gzip size…
8:54:16 PM: dist/spa/index.html 0.41 kB │ gzip: 0.27 kB
8:54:16 PM: dist/spa/assets/index-rLDicTZn.css 76.32 kB │ gzip: 12.62 kB
8:54:16 PM: dist/spa/assets/index-aCHuE8Zf.js 437.40 kB │ gzip: 125.23 kB
8:54:16 PM: ✓ built in 4.69s

No errors

HOWEVER, it won’t continue to deployment

[eewew]

8:43:34 PM: ✓ built in 3.87s

9:00:14 PM: Failed during stage ‘building site’: Command did not finish within the time limit

9:00:14 PM: Execution timed out after 17m59.926261593s

9:00:14 PM: Failing build: Failed to build site

9:00:14 PM: Finished processing build request in 18m24.256s

[nathanmartin]

@eewew Relevant Support Guide:

https://answers.netlify.com/t/support-guide-hung-or-stuck-but-seemingly-successful-build/99

You can try what it suggests towards the end…

@laura

If you don’t already know what the process is, it can be a bit tricky to find it, but it is specific to your code. You might try appending && ps auxw ; false to your build command to see if you can get a listing of what’s there so you can make sure your build doesn’t start it, or make sure that process exits.

If I had to guess based only on your build log, it may be related to whatever this is…

@eewew

8:54:12 PM: Bot status monitor ready as Apex#5250
8:54:13 PM: Discord bot logged in as Apex#5250

[eewew]

I removed that, and yet it still won’t build

[eewew]

nevermind got it to work!

[nathanmartin]

@eewew Excellent.

The key point which is addressed in the Support Guide is that it happens when a process remains stuck running, and you can try and identify what that process may be by appending && ps auxw ; false to your build command.

As once you know what it is you can deal with it by ensuring it closes, or removing it etc.