nf-test with conda locally is....slow.....even if ...
# meta-omics
e
nf-test with conda locally is....slow.....even if I've used the same libraries before, it's creating a new environment for different modules.... 😕
😓 1
👀 1
m
There are solutions for that
e
I do that already :'D
m
oh
so different modules, but same libraries in the modules?
e
Yep, even though it was the same exact env, it was recreating it when called from different modules.
m
It would be interesting to know if this is coming from nextflow or from nf-test
e
I think nf-test, without putting my hand in boiling water
m
I'm wondering, is this issue still the same if you run just vanilla Nextflow?
e
lemme check right away
damn it's nextflow!
let me try an older version
m
I think @Edmund and I stumble into this issue
e
Switching to 24.10.8 also tried downloading the same env for the 2nd module. switching to 24.04.02 re-downloaded the first module env again, but DIDN'T for the next modules!!!
Let me pinpoint which version exactly introduced this behaviour
cc @Phil Ewels as you are not on this channel but I think this will be of interest to you
👀 1
e
Verdict: 24.10.0 works as intended; uses already downloaded conda envs, for different modules 24.10.1 will try to download same conda env, for different modules
m
nice investigation
Could you create an issue for this on the Nextflow side?
e
On it!
🎉 1
Next release I guess 😄
✅ 2