Jeff,
fwiw, it is possible to save some bandwidth (~4x) with the --depth option
full clone:
git clone https://ggouaillar...@github.com/open-mpi/ompi-tests.git
Cloning into 'ompi-tests'...
remote: Counting objects: 32016, done.
remote: Total 32016 (delta 0), reused 0 (delta 0), pack-reused 32016
Receiving objects: 100% (32016/32016), 61.31 MiB | 645.00 KiB/s, done.
Resolving deltas: 100% (20719/20719), done.
Checking out files: 100% (9221/9221), done.
last commit only :
git clone --depth=1 https://ggouaillar...@github.com/open-mpi/ompi-tests.git
Cloning into 'ompi-tests'...
remote: Counting objects: 10687, done.
remote: Compressing objects: 100% (4667/4667), done.
remote: Total 10687 (delta 4972), reused 9595 (delta 4477), pack-reused 0
Receiving objects: 100% (10687/10687), 13.29 MiB | 673.00 KiB/s, done.
Resolving deltas: 100% (4972/4972), done.
Cheers,
Gilles
On 4/26/2016 12:03 AM, Jeff Squyres (jsquyres) wrote:
On Apr 25, 2016, at 9:50 AM, Gilles Gouaillardet
<gilles.gouaillar...@gmail.com> wrote:
and fwiw, Jeff uses an internally mirrored repo for ompi-tests, so it Cisco
clusters should use the latest test suites.
Correct. My local git mirrors update nightly.
FWIW: This made a *huge* difference when we were using SVN for ompi-tests. An
individual SVN checkout across the network was reeeaaaalllllyyyyy slow; it was
*significantly* faster to do a local SVN checkout.
I'm sure it's still faster to do a local git clone, but I don't know offhand if
the amount of speedup is compared to a github.com clone of ompi-tests.
