Consider using depth of 1 when automatically cloning a git repo

reframe-hpc / reframe

A powerful Python framework for writing and running portable regression tests and benchmarks for HPC systems.

https://reframe-hpc.readthedocs.org

BSD 3-Clause "New" or "Revised" License

214 stars 102 forks source link

Consider using depth of 1 when automatically cloning a git repo #3053

Open teojgo opened 9 months ago

teojgo commented 9 months ago

This would make cloning much faster

vkarak commented 9 months ago

Agree with that, but you mean we should do that in the unit tests or in the osext utility?

teojgo commented 9 months ago

On osext we can do it using the opts. I was thinking when we use a git repo as the source of the code. On seconds thought though, in tests where we switch to a git branch as a subsequent command then the branch is not there since the depth does not cover it, unless we enrich the source syntax to include a branch and/or depth by itself.