https://nf-co.re logo
Join Slack
Powered by
I notice that when I run `nf-core pipelines lint` ...
# tools
n
I notice that when I run 
nf-core pipelines lint
locally, it takes much longer than when it happens on CI. Is there some magic in the CI to make it faster that I could replicate locally?
m
Are you sure you use the same version of tools?
n
No 😄 but I have observed this for a while, all of the module linting and subworkflow linting takes very long
I am currently using 
<http://4.0.3.dev|4.0.3.dev>
locally
m
and in the CI?
n
4.0.2
but I think this is more a problem with my local setup, because it has been ongoing for a while, also with 4.0.2
m
if you run it with 
n-core --verbose p l
you will get a bit more insight where it is stuck.
n
ok, I will give that a try the next time i lint
it seems like 
git checkout
is taking a while every time
m
do you see which checkout command specifically?
n
checking out master on modules
Unrelated: do I assume correctly that if I fix linting with 
<http://4.0.3.dev|4.0.3.dev>
it is not compatible with the CI running at 
4.0.2
?
m
depends, but it is risky 🙂
ohno2 1
n
any idea why I get 
KeyError: 'manifest.name'
after switching back to 4.0.2 and attempting to lint?
m
clean your cache in 
~/.config/nfcore
(we put parsed configs there and changed a bit of the parsing in 4.0.3)
👍 1
n
interestingly, 
~/.config/nf-core
is the cache for the modules repo, the cached workflow configs are in 
~/.nextflow/nf-core
(I only know this because I was watching the verbose output for a while).
m
ah, okay, we use the nextflow cache in that part then 🙂
n
running 
git gc
in 
~/.config/nf-core/modules
did not make things faster, fyi
2 Views
Open in Slack
PreviousNext
Powered by