add GPUS testing possibility

[maxulysse]

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 pipeline conventions in the contribution docs
• If necessary, also make a PR on the nf-core/sarek branch on the nf-core/test-datasets repository.
• Make sure your code lints (nf-core pipelines lint).
• Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
• Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
• Usage Documentation in docs/usage.md is updated.
• Output Documentation in docs/output.md is updated.
• CHANGELOG.md is updated.
• README.md is updated (including new tool citations and authors/contributors).

[nf-core-bot]

Warning

Newer version of the nf-core template is available.

Your pipeline is using an old version of the nf-core template: 3.0.2.
Please update your pipeline to the latest version.

For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation.

[famosab]

I think this looks good but I am not an expert on anything related to GHA haha

[famosab]

Do we also need to extend the nf-test.config to include gpu settings (similar to modules repo) or does nextflow do this automatically?

[famosab]

Something like this in the nextflow config

gpu {
        process {
            withLabel: process_gpu {
                ext.use_gpu = true
            }
        }
        docker.runOptions = '-u $(id -u):$(id -g) --gpus all'
        apptainer.runOptions = '--nv'
        singularity.runOptions = '--nv'
    }

[famosab]

or a test profile for gpus

[maxulysse]

Possibly, I think that can be included in the parabricks PR.
I did just have a go at the GHA

[FriederikeHanssen]

what happened to the checksums?

[maxulysse]

Famke removed some cram.stats, because they were unstable, so I removed them all