-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exp
: CI runs require unshallow clone (fetch-depth: >1)
#3416
Comments
For CML workflows, In non-CML cases (probably worth mentioning in dvc.org docs), unshallow clones are needed ( |
I never noticed |
What about creating a new section in https://dvc.org/doc/user-guide/troubleshooting , catching the specific exception on DVC side, and make it point to that URL |
exp
: CI runs require unshallow clone (fetch-depth: >1)
Which I'm guessing mostly Thanks |
No, unfortunately even |
OK. Hmmm I'm not sure we need to much of a change other than perhaps a small note in https://dvc.org/doc/user-guide/experiment-management/experiments-overview and https://dvc.org/doc/command-reference/exp (/init). Seems like an edge case, or have you noticed this being a common issue out there outside of CML? https://cml.dev/doc/cml-with-dvc should probably note this and recommend |
It's an issue in many CI scenarios (with or without CML) because the default behavior in both GitHub (https://github.com/actions/checkout) and GitLab (https://docs.gitlab.com/ee/ci/large_repositories/#shallow-cloning) is a shallow clone. |
definitely docs in both because
Makes sense to mention in: |
* contrib: shorten guide - follow-up to #220 * dvc: use ci --unshallow - vis. iterative/dvc.org#3416 (comment)
Summary:
dvc exp
commands will not run in CML or other Github actions (and probably the same on other Git servers?) because they will only fetch the head commit by default, which is insufficient for internalgit merge
s. The solution is in iterative/dvc#7547 (comment).Not sure where to document this or even whether it belongs in DVC, CML, or both. @casperdcl Maybe you have thoughts?
The text was updated successfully, but these errors were encountered: