Closed ashishsingh18 closed 4 years ago
I wonder if this is a factor of the initial repo depth? I am seeing the git clone
command on Travis (all platforms) is taking ~250 seconds for a depth of 50.
Was that a simple clone, or with any options (ie., depth)?
This is likely due to network bandwidth and any issues with Github, not with the content of our repo.
time git clone https://github.com/CBICA/CaPTk.git
Cloning into 'CaPTk'...
remote: Enumerating objects: 7628, done.
remote: Total 7628 (delta 0), reused 0 (delta 0), pack-reused 7628
Receiving objects: 100% (7628/7628), 139.23 MiB | 28.86 MiB/s, done.
Resolving deltas: 100% (4458/4458), done.
real 0m6.447s
user 0m3.970s
sys 0m1.216s
Please see the usage of the environment variable GIT_LFS_SKIP_SMUDGE
in https://github.com/CBICA/CaPTk/blob/master/azure-pipelines.yml
Describe the bug Fresh cloning of Captk on a Linux system takes a very long time (several hours)
To Reproduce Fresh clone of Captk on a clean system