Updated test data paths batch 8

[GallVp]

PR checklist

Closes #XXX

• Updated test data paths batch 8
• 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:
  • For modules:
    • nf-core modules test <MODULE> --profile docker
    • nf-core modules test <MODULE> --profile singularity
    • nf-core modules test <MODULE> --profile conda
  • For subworkflows:
    • nf-core subworkflows test <SUBWORKFLOW> --profile docker
    • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
    • nf-core subworkflows test <SUBWORKFLOW> --profile conda

[GallVp]

A conda package seems to be broken?

https://github.com/nf-core/modules/actions/runs/10172683953/job/28139842853#step:14:175

[SPPearce]

A conda package seems to be broken?

https://github.com/nf-core/modules/actions/runs/10172683953/job/28139842853#step:14:175

Strange, it is listed in the recipe.
It was passing the tests previously, it is a very tricky package to actually use. One option is to make an issue for any failures and leave them out for the moment.

I've just tried explicitly adding the package to the environment.yml, but I'm not able to run the current version in conda on gitpod either.

[GallVp]

For now, going to leave fastqscreen out. Issue raised: #6075

[GallVp]

Excluded bowtie2/build to avoid nf-test trigger for fastqscreen_fastqscreen