Pin nf-test in the CI instead of installing the latest release - #127
Conversation
The install script resolves the latest release through the unauthenticated GitHub API, which is rate limited on shared runners. That failed a job with `curl: (22) The requested URL returned error: 403` before a single test ran. nf-core/setup-nf-test takes a pinned version, so no API call is needed, and it caches the download in the tool cache. Version 0.9.5 is what the CI has been resolving to anyway. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Not a comment about the specific changes here (which look good), but about the action files in general: most of the actions are out of date. We can set up dependabot to automatically create PRs to bump the action versions. I can set that up for you if you like, since I'm already doing it for a few other repos. |
|
Thanks — agreed, and I've opened #134 with a If you'd rather set this up yourself with whatever conventions you're using in the other repos, say the word and I'll close #134 in favour of yours — no attachment to my version. |
Problem
The
Install nf-teststep runs:wget -qO- https://code.askimed.com/install/nf-test | bashWithout a version argument that script resolves the latest release through
https://api.github.com/repos/askimed/nf-test/releases/latest— unauthenticated. On shared GitHub runners that call gets rate limited, and because the script runs underset -ethe whole job dies before a single test runs:This happened on the CI of #124. It is unrelated to the pipeline itself and will come back at random.
Change
Use
nf-core/setup-nf-testwith a pinned version, mirroring how the workflow already installs Nextflow withnf-core/setup-nextflow:GITHUB_TOKENis set on that step so any API access it does make is authenticated0.9.5is the version the CI has been resolving to anyway, so nothing changes about what is tested.Note
This touches the same workflow file as #124, but a different section (that PR only changes the
NXF_VERmatrix), so the two merge cleanly in either order.