pre-commit ci failing to clone

[chai-unitary]

We have configured pre-commit ci to run on PRs made to our private-repo since few weeks. It worked fine until yesterday.

Since yesterday, pre-commit ci job is failing during the clone stage with following message on GH action

Error during clone

Details reveal that pre-commit ci job is timing out

fetch attempt 1...
    => timeout after 30s
fetch attempt 2...
    => timeout after 30s
fetch attempt 3...
    => timeout after 30s

[asottile]

how large is your repository? was this perhaps during github's outage yesterday?

[chai-unitary]

not super large. how do you quantify size though?

not related to yesterday's outage as its failing even now

[asottile]

can you provide a link to the run (the runs are private for private repos) -- I can debug a little bit from that but might need some additional information

[chai-unitary]

https://results.pre-commit.ci/run/github/191402629/1686156604.VNc1vTztSpaG01KybqyxiQ https://results.pre-commit.ci/run/github/191402629/1686150689.sepc5hScTbu0Ay-4yXhsmg

[asottile]

hmmm looking at historical runs I see a slow uptick in clone time -- and some where individual tries timed out

how large is the repo? (or maybe it has lots of files?)

[chai-unitary]

Size of git repository

 du -sh .git/
1.1G    .git/

Number of lines in repo

git ls-files | xargs cat | wc -l
4238757

Number of files

 git ls-files | wc -l
    2123

Are there limits on the size & is that causing time out?

[asottile]

the limit is just on time -- 30 seconds to make a clone. 1G is probably pretty close to taking 30 seconds.

would you like me to take a peek at the repo and see if there's anything glaringly obvious that may help with the performance?

[chai-unitary]

Thanks for the prompt response. We will try and address the 1G size issue and get back in case we still have difficulties. Closing this topic as the root-cause [size>1G] seems to be identified