Does anyone run automated

-resume

tests which tests everything remains cached on a second run? Do we have an implementation of that? ( I just had a module delete my inputs, because tests don't catch it's deleting the input. )

I think bug's in the cleanup: find -L follows the staged input symlinks (including symlinked subdirs) into your source data and -delete wipes the real files. Probably fix by dropping the -L so only the intermediate files krakenuniq-build actually wrote get cleaned.

Oh, I have a rough idea how to fix it. I just need to double check, but for that I need my pipeline to run through. I updated a bunch of modules and now I'm getting errors because input signatures have changed

Ahh, gotcha