You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When executing dvc exp run (with or without --temp, also when specifying --single-item), it checks out all cached deps (and outs?) of stages listed in the dvc.yaml file of the stage specified as target, and also all stages in other dvc.yaml files of other pipelines in the same DVC project.
Reproduce
Expected
Command dvc run exp target should only checkout the data files specified as deps of the target to run, plus maybe all previous stages in the pipeline that produce these if necessary and when --single-item is not specified. Especially when using the --temp option (i.e., --queue + --run-all), this results in a long wait for dvc to check out many data files from unrelated pipelines / stages.
Bug Report
Description
When executing
dvc exp run
(with or without--temp
, also when specifying--single-item
), it checks out all cached deps (and outs?) of stages listed in thedvc.yaml
file of the stage specified as target, and also all stages in otherdvc.yaml
files of other pipelines in the same DVC project.Reproduce
Expected
Command
dvc run exp target
should only checkout the data files specified asdeps
of thetarget
to run, plus maybe all previous stages in the pipeline that produce these if necessary and when--single-item
is not specified. Especially when using the--temp
option (i.e.,--queue
+--run-all
), this results in a long wait fordvc
to check out many data files from unrelated pipelines / stages.Environment information
Output of
dvc version
:Additional Information (if any):
The text was updated successfully, but these errors were encountered: