<@U024DTV3HUH> <@U0919399YT1> Let's move the discu...
# mcmicro
j
@Adam Taylor @Alex Let's move the discussion on #122 here so we can all put our heads together
@Adam Taylor As I understand it you have one larger goal, which is to run on Sage's nf-tower. Seems like the required changes fall into 2 separate pieces: 1) Changes to support the older nextflow version you're stuck on; 2) Porting our
exec
processes to
script
for cloud executor compatibility. Is that accurate?
I propose breaking this up into 2 separate PRs to make it easier to follow later. Alex has offered to work that up.
We need to do item 2 regardless
a
I agree that this should be split up
j
For the NXF_VER issue, Alex is putting together the PR to make the syntax compatible with 24.10.9, but we don't want to also downgrade our nf-schema version which seems like it's going to be a headache in the long term. This means we won't be able to add NXF_VER=24.10.9 the test matrix. However I propose that one could add a separate job entry to
nf-test.yml
that runs just
tests/default.nf.test
under
NXF_VER=24.10.9
, with a dedicated profile that sets the
nf-schema
plugin version to 2.4.2 or whatever is compatible.
🎉 1
(possibly marking that extra test as soft-fail)
a
That’s fine. I can downgrade the schema version in a profile/ the seqera platform launch config
a
@Adam Taylor we implemented changes to mcmicro that should address the issues you are having. Please notice that we will not be officially supporting <25.0.0 so if you want you can wither test locally that this works or open a PR with an optional test on the actions. if you still run into issues let us know!
👀 1
Also if the changes fix the issue feel free to close the original PR
a
Thank you! Will test and report back