-
Notifications
You must be signed in to change notification settings - Fork 6
Report BUSCO errors #194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report BUSCO errors #194
Conversation
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.2.1. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
DLBPointon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
If this is as wide spread an issue as the attached issue implies, then would it make sense to push up to nf-core too? Surely there will be people in the same boat?
Good call. Mahesh was happy to approve the request :) I've force-pushed the branch here. Now it's as simple as a |
Closes #178
My solution is simply to return a non-zero code if there is "Run failed; check logs" in the output file.
Note that this leaves Prodigal errors off the hook, as these are reported as "No genes found" (cf #147 (comment))
PR checklist
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).