DennisKraaijeveld
commented
2 years ago I have exactly the same going on. I am on Standard/Standard plan and since 2 days fresh build will take forever. Sometimes it will finish after 25-30 minutes.
10:40:15 AM:
info [gatsby-plugin-perf-budgets] hooking into webpack
10:40:25 AM:
warning warn - Preview features are not covered by semver, may introduce breaking changes, and can change at any time.
10:40:25 AM:
warning warn - You have enabled the JIT engine which is currently in preview.
10:40:25 AM:
warning ⠀
10:41:05 AM:
Webpack Bundle Analyzer saved report to /usr/src/app/www/public/report.html
10:41:05 AM:
success Building production JavaScript and CSS bundles - 50.349s
10:41:32 AM:
success Building HTML renderer - 27.319s
10:41:32 AM:
success Caching Webpack compilations - 0.001s
10:41:32 AM:
success Execute page configs - 0.093s
10:41:34 AM:
success run queries in workers - 1.793s - 307/307 171.24/s
10:46:34 AM:
warning This is just diagnostic information (enabled by GATSBY_DIAGNOSTIC_STUCK_STATUS_TIMEOUT):
10:46:34 AM:
- Activity "build" of type "hidden" is currently in state "IN_PROGRESS"
10:46:34 AM:
Gatsby is in "IN_PROGRESS" state without any updates for 300.000 seconds. Activities preventing Gatsby from transitioning to idle state:
10:46:34 AM:
Process will be terminated in 1500.000 seconds if nothing will change.I wanted to open an issue, but I guess we have something similar.
I am also using createRemoteFileNode to download and optimise remote images. I will run a build without that to see what happens.
LekoArts
NickBarreto
ashhitch
startinggravity
pieh
buzinas
askibinski
bkaldor
ghost
github-actions[bot]
sferg989
smujmaiku
bakervin
SebastianMera
seanho96
thisispvb
haneabogdan
sensedrive
ansmlc
wardpeet
If you're coming new to this issue, please see this first: https://github.com/gatsbyjs/gatsby/issues/34051#issuecomment-979882343
Preliminary Checks
Description
Gatsby's build process is hanging and not completing. I suspect the issue is with Sharp, as my site has quite a few images, and I saw this brought up in a previous issue, #33557.
When I upgraded to v4 I initially had no issues. However, the next day my builds all started going exceeding Netlify's maximum build time of 30 minutes.
I mentioned this problem in the thread to the other issue, as others apparently had the same problem where
run queries in workersseems to take longer than expected.This issue is difficult to reproduce because I think in part it is to do with the scale of my site, which is moderately large and has ~1600 images. There must be something that isn't quite right in the worker process because my builds on netlify went from roughly taking around 13 or 14 minutes, to exceeding the build limit every time.
To try and diagnose the issue I tried a local build, which while it took a long-ish time, did actually complete
Since @LekoArts suggested that Gatsby Cloud's build process is better optimised for processing images, I thought I'd give that a go.
After trying out a build in Gatsby Cloud, I had no build problems at all and the whole site build with a clear cache in 7 minutes. OK, I thought, seems like the problem isn't so much with Gatsby, but in how Netlify is interacting with v4's worker process.
However, the next push I ran into the problem once again, this time in Gatsby Cloud. The bottom end of Gatsby Cloud's logs are useful, because they give me a little more information than Netlify:
The fact that a full, uncached build on Gatsby Cloud can run in 7 minutes, suggests to me that actually the issue isn't one of scale, but that the worker process is hanging, but only sometimes.
Is it to do with incremental builds? Maybe. I am using the preserved download cache, because as I said my site has quite a few images which are coming from a custom source plugin (which is relatively simple, and contains all the image links from AWS that are passed over to createRemoteFileNode).
To test things out once I had the first timeout on Gatsby Cloud, I tested a manual deploy without clearing the cache. I was hoping the process would hang again so I'd know the issue was with the cache and incremental builds, but alas, it did not. The whole build was completed in 6 minutes. Strangely, the issue does appear to occur on Netlify more frequently than not, and happens more occasionally in Gatsby Cloud. It may be to do with build process resources, because I just signed up to Gatsby Cloud, and so am in the free preview of performance builds.
Are there other diagnostic tools I can use to more closely inspect the build process? How would I be able to see which process is failing or never finishing?
Reproduction Link
I can't seem to reproduce this error as it is intermittent
Steps to Reproduce
gatsby buildin either Netlify or Gatsby CloudExpected Result
gatsby buildshould eventually finish and build the siteActual Result
The state
run queries in workersnever finishes/moves on tomerge worker state, the build eventually times out and fails.Environment
Config Flags
PRESERVE_FILE_DOWNLOAD_CACHE: true