Fix the always-empty Nextflow version in the CodSpeed workflow - #4442
Open
FelixKrueger wants to merge 1 commit into
Open
Fix the always-empty Nextflow version in the CodSpeed workflow#4442FelixKrueger wants to merge 1 commit into
FelixKrueger wants to merge 1 commit into
Conversation
The version: input was ${{ github.event.inputs.nextflow-version ||
matrix.nextflow-version }}, copied from pytest.yml. That workflow declares
both operands -- a workflow_dispatch input and a matrix axis -- but
codspeed.yml has a bare workflow_dispatch: and no strategy:, so the
expression is always empty and explicitly overrides the action's own
latest-stable default with nothing.
setup-nextflow then reports "Could not retrieve Nextflow release matching ."
and attributes it to the nf-co.re endpoint, which is healthy; the empty
string after "matching" is the actual tell.
Dropping the with: block lets the action's default apply. Every run of this
workflow has failed since at least 2026-07-29, on main and dev as well as on
PR branches.
FelixKrueger
force-pushed
the
fix/codspeed-nextflow-version
branch
from
August 12, 2026 10:24
8fcd5e3 to
cb623e0
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
Hooray! CodSpeed harness just leveled up!The base and head of this comparison were measured with different runner settings, so their benchmark values are not directly comparable. What changed between base and head:
Re-run the base with the same settings to get a valid performance comparison. Comparing 
Footnotes |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
codspeed.ymlpassesversion: ${{ github.event.inputs.nextflow-version || matrix.nextflow-version }}tosetup-nextflow, but this workflow declares neither operand — itsworkflow_dispatch:is bare and the job has nostrategy:— so the value is always an empty string, which explicitly overrides the action's ownlatest-stabledefault. The job fails atInstall NextflowwithCould not retrieve Nextflow release matching .and has never completed. Dropping thewith:block lets the default apply. Happy to pin an explicit version instead if you'd rather keep the benchmarks on a fixed Nextflow.Detail (AI-assisted)
pytest.yml, which does declare both operands (aworkflow_dispatchinput and anextflow-versionmatrix axis), so the same expression resolves there.matchingis the actual tell.failureand 1 ×cancelled, back to 2026-07-29, onmainanddevas well as PR branches.