It's already fixed in dev, but the action runs fro...
# nextflow-nightly-tests
m
It's already fixed in dev, but the action runs from main. (Needed a uv setup step)
👍 1
🙏🏻 1
p
Looks like it's running off my fork though..?
Which was a bit behind
dev
but not far
m
hmm, weird, I thought i had these fixes (the
--all-extras
should only be needed for developing)
ah, yes, I had a PR to first test it on your fork https://github.com/ewels/nf-core-tools/pull/8
p
ah nice
hah I'm doing the same
--project
stuff now trying to fix the paths. I'm playing with similar
m
if you are tired of testing, I can take over, I think I had similiar issues over at tools when we switched to uv.
p
yeah I'm getting there
Trying to throw claude at it but not getting far
working on
main
on my fork
I added in a cache flag step that skips the test if we have had a previous successful run with that nextflow commit
✅ 1
I'm not sure that I buy this?
Ok if you take over @mashehu?
👍🏻 1
m
I added in a cache flag step that skips the test if we have had a previous successful run with that nextflow commit
will not add this for now, because even though nextflow might not have changed nf-core tools might have.
p
yeah but tools runs its own CI on changes
so I figured that was complementary
m
but not against the
master
version of nextflow
p
true.. easy enough to make the cache check also include the tools dev commit if you want
👍🏻 1