I’m having this problem too. How do I get help with it? It would be helpful if this discussion included details about the outcome so others can benefit.
We are also having this problem. We opened a support request, but haven’t heard back yet. We’ve temporarily switched back to the Ubuntu 12 container as a workaround, but would love to get back on 14.
Discussion with support is still ongoing. I’ve claimed that there’s something wrong with git-lfs but looks like they think different way(like repository is too big, etc…)
Yes, I also have many files in git-lfs and I know it’s very slow. However, when I looked into the build log, git-lfs in the container behaved like “stuck” instead of “slow”. I guess some constant networking issue is there between CircleCI and Git LFS.
I know that this kind of issue takes a lot of efforts to investigate, so my possible workaround is just to remove git-lfs from my build image(even when circle.yml cannot be loaded) as fortunately my test suites don’t depend on git-lfs’ed files.
Problem is, I still haven’t succeeded to make them understand my exact situation (and maybe what the heck git-lfs is).
I was able to figure out what my issue was and now git lfs is working for me in CircleCI. This may not apply to you, but it’s something you can check. When I checked out the repo separate from CircleCI I noticed some of the files I was tracking with LFS gave an error message “Pointer file error: Unable to parse pointer at:”. When cloning in CircleCI it just hung on these files indefinitely instead of giving an error for some reason. I think I got into this situation by using git mv to move files from a path that was not tracked by git-lfs to a path that was. I think as a result the git-lfs files were in a weird state in git. To fix this I tried deleting the files and readding them. The error message went away and CircleCI became unstuck while cloning.
What was helpful in discovering this was SSHing into the CircleCI VM and setting these flags, then running the various git commands CircleCI uses to clone to the commit. I saw that it got stuck after one file.