Closed aksarkar closed 3 months ago
Thanks @aksarkar for posting this issue.
Briefly, this is the best redun can do given how dynamic it's execution is. The way it implements dryrun is to try and execute the workflow from cache as far as it can until it reaches the frontier of jobs that have never been run before. It'll either tell you the entire workflow is uptodate, or halt saying which job(s) require running.
make -n
is able to report more in its dryrun mode, because make's DAG can be entirely determined statically / upfront.
I'm happy to update the redun docs to make this distinction more clear, if that would help.
OK, it would be helpful to make the documentation more clear about this case.
If I run the following example
I get the following output
However, I would expect to see a report on how much of the entire DAG reachable from the entry point I queried would be re-run vs retrieved from cache. This is for example what
make -n
does.