Improvement to nf-tests for 2.1.0#630
Conversation
|
tlitfin
left a comment
There was a problem hiding this comment.
🚀 - Great change on path to adding real tests. Worth checking with @JoseEspinosa before merging due to the slight change in runner resourcing but otherwise LGTM.
JoseEspinosa
left a comment
There was a problem hiding this comment.
I have mixed feelings with this PR. I think it is nice to catch things like broken containers, missing tools, or version mismatches that could silently cause downstream failures but on the other hand, I wonder whether the value justifies the CI cost, as the tests are run with any commit added to a PR...
JoseEspinosa
left a comment
There was a problem hiding this comment.
Actually, it might be nice to have the opinion of someone from infrastructure, maybe @mashehu could chip in and provide his opinion 🙏
|
Comparing the old workflow with the new one, pulling real containers increases total walltime by ~4x. One potential compromise would be to only run the workflow with
|
|
@jscgh also had a nice suggestion that we could run the actions workflow after PR approval if we are concerned about resourcing. |
Resolves #365
meta.idandmeta.model(solves filename clash failure)PR checklist
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).CHANGELOG.mdis updated.