set conda.enabled=true to fix Conda testing

[pinin4fjords]

This is my proposal to address conda testing failures, with reference to nextflow-io/nextflow#3073.

Motivate by failure discussed in https://nfcore.slack.com/archives/CJRH30T6V/p1665736973295039, #2167.

In summary, the Conda profile is no longer driving Conda environment creation and usage, which was noted previously, so I think we just need to set this param explicitly.

PR checklist

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added a new tool - have you followed the module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Emit the versions.yml file.
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • PROFILE=docker pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware
  • PROFILE=singularity pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware
  • PROFILE=conda pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware

[jfy133]

LGTM but I would like a sceond pair of 👀 : , this also needs to be updated in the nf-core pipeline template if you're up for that @pinin4fjords ? (in the nextflow.config iIIRC

[grst]

I'm a bit out of the loop, but doesn't this make the params.enable_conda obsolete?

[JoseEspinosa]

Yep was about to say the same

[jfy133]

Would we not need it still for backwards compatibility for people not yet on 22.10?

[edmundmiller]

Should we have added a check for the nextflow version?