Git clone fails with signal: killed

Hey Netlify Team,

I’d love to move website deployment from Github Pages to Netlify. :slight_smile:

My build fails in the initializing after about 35 min. (multiple attemps, same outcome) with signal: killed:

I do have quite a number of images hosted on Git LFS though.


Log:

9:25:51 PM: build-image version: 9470eb4bcb76aed090584ca3beb7b71f813fe63b (noble)

9:25:51 PM: buildbot version: 55ba56fdd1d6993bde37284ad04ed90fea91a4cc

9:25:52 PM: Fetching cached dependencies

9:25:52 PM: Failed to fetch cache, continuing with build

9:25:52 PM: Starting to prepare the repo for build

9:25:52 PM: No cached dependencies found. Cloning fresh repo

9:25:52 PM: git clone --filter=blob:none […]
.
.
.
Downloading content/[…].webp (5.1 KB)
: signal: killed

10:01:40 PM: Error checking out to refs/heads/dev

10:01:40 PM: Failing build: Failed to prepare repo


Site ID: 8aa72bca-12a4-4dd1-8903-fea2705f73ef

I am currently in the starter plan.

Could you help me out with that?

Best

Toni

Where exactly are all the files listed in the logs stored: Deploy details | Deploys | edler-wohnraum | Netlify? Are they in your repo? Are you using LFS, a submodule or something else?

Thanks for checking, hrishikesh! :slight_smile:

The files are part of the repo and located in the Github LFS since we don’t need any versioning on them.

Hi, @KaeptnBalu.

It looks like the clone just times out. To test this, I have increased the build time limit for this site from 30 to 60 minutes. Please note, once the site builds successfully we will save the cloned repo to the site’s build cache and future clone should be incremental (meaning only the initial clone should take this long).

Also, when using repositories with Git LFS enabled at Netlify, there is an environment variable that should be used in the site’s configuration settings at Netlify:

GIT_LFS_ENABLED=true

This setting is found under Site configuration >> Environment variables in the web UI at Netlify. Note, this environment variable must be define in the UI and not in netlify.toml (because netlify.toml is only readable after cloning and this environment variable is needed before the clone begins).

Would you be willing to please try building again now and let us know if the site build is successful or not?

Also, as an aside and not to be overly pedantic, but files using Git LFS still are version controlled. The use of LFS changes the clone behavior but all changes to those files are still tracked.

Hey Luke,

Thanks for increasing the build time!

The checkout for the images was about 85% complete within that hour. Would it be possible to increase the build time to 90 or even 120 minutes?

Also, thanks for correcting me on the Git LFS versioning. :slight_smile:

I’ve bumped it to 2 hours. Could you try now?

Hey @hrishikesh ,

I get e-mail from savyybot to mark a solution. I marked and re-marked your reply already.
—> Why do I still get these emails?

This is an automated message - we saw you posted a question in our forums which is likely solved, but we didn’t see you mark a solution. Marking questions as solved greatly helps other people find answers to their questions.

Not sure about it, but I added an exclusion to skip notifying on this thread.