Fix nf-core download test

[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/rnaseq 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).

[github-actions]

This PR is against the master branch ❌

• Do not close this PR
• Click Edit and change the base to dev
• This CI test will remain failed until you push a new commit

---

Hi @maxulysse,

It looks like this pull-request is has been made against the maxulysse/nf-core_rnaseq master branch.
The master branch on nf-core repositories should always contain code from the latest release.
Because of this, PRs to master are only allowed if they come from the maxulysse/nf-core_rnaseq dev branch.

You do not need to close this PR, you can change the target branch to dev by clicking the "Edit" button at the top of this page.
Note that even after this, the test will continue to show as failing until you push a new commit.

Thanks again for your contribution!

[maxulysse]

I'm seeing this in the download GHA:

Pulling Singularity image https://community-cr-prod.seqera.io/docker/registry/v2/blobs/sha256/63/6397750e9730a3fbcc5b4c43f14bd141c64c723fd7dad80e47921a68a7c3cd21/data [cache /home/runner/work/rnaseq/rnaseq/./singularity_container_images/community-cr-prod.seqera.io-docker-registry-v2-blobs-sha256-63-6397750e9730a3fbcc5b4c43f14bd141c64c723fd7dad80e47921a68a7c3cd21-data.img]

and I'm wondering where this is coming from since I don't have any container pointing to community-cr-prod.seqera.io anywhere

[maxulysse]

it works: https://github.com/nf-core/rnaseq/actions/runs/11496567950/job/31998439226

[pinin4fjords]

Until we figure out the proper tools fix I think this is an OK workaround

[pinin4fjords]

Proper fix is here: nf-core/tools#3244

[pinin4fjords]

(so we can probably revert this next release)