Hi Guys and Girls
Like every 5th build, it can’t fetch the cache.
This is how the init-logs of building looks like if it is able to use the cache:
11:52:52 AM: build-image version: c11c0eb9939c949586b0f78302107908b668a11e (focal)
11:52:52 AM: buildbot version: 89da9f761f300da7c12c5a46a3cfeccfbd36fe9e
11:52:52 AM: Fetching cached dependencies
11:52:52 AM: Starting to download cache of 6.9GB
11:54:03 AM: Finished downloading cache in 1m10.107s
11:54:03 AM: Starting to extract cache
11:54:20 AM: Finished extracting cache in 17.679s
11:54:21 AM: Finished fetching cache in 1m28.187s
And this is how it looks when it’s failing:
11:34:46 AM: build-image version: c11c0eb9939c949586b0f78302107908b668a11e (focal)
11:34:46 AM: buildbot version: 89da9f761f300da7c12c5a46a3cfeccfbd36fe9e
11:34:46 AM: Fetching cached dependencies
11:34:46 AM: Starting to download cache of 6.9GB
11:35:16 AM: Failed to fetch cache, continuing with build
11:35:16 AM: Starting to prepare the repo for build
11:35:16 AM: No cached dependencies found. Cloning fresh repo
I don’t know hot to debug this and I think it’s out of my possibility to fix this issue. Since I have so many images on this website, it mostly fails to build within time.
Any Idea what can cause this? Thanks for any help!
Without any site links, IDs or other useful indentifying informatiion, we cannot help much. Please provide some details.
You need to see full logs?
Yes, you could attach a link to the log?
Your problem lays here…
. 2:31:04 PM: Error: ENOENT: no such file or directory, lstat ‘/opt/build/repo/dist/stoeberecke/’
I think you should check where you are having Netlify build your site. I recommend you checkout this guide as well as it should help, and for further assistance a link to your repo [Support Guide] Debugging Netlify site builds
Quite sure it’s not that. This Error only appears because it can’t fetch the cache (where this folder exists) and doesn’t influence the build further down the ladder. The cache download/fetch happens in the initialize-phase and not while building.
@hrishikesh Could you please have a look at it?
Unfortunately, you’ve deleted the exact lines from the logs that would show your deploy IDs and your current list of deploys doesn’t show the problem easily. Can you please share a link to the deploy where the problem happened?
This was a bug which should be fixed as of 2 days ago. Let us know if you’re still seeing issues.
Yes it didn’t happen anymore. Thanks.
Glad to hear it! Thanks for coming back.