-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fix mkfastq #253
Fix mkfastq #253
Conversation
|
Looks like the first shard worked correctly with the mkfastq tests but the others are "empty" because there are no more tests to run. I would expect them not to run or to end successfully. Perhaps it is worth asking in nf-test. |
@edmundmiller not familiar with the new sharding system, can you take a look? |
I haven't seen this either. Probably just merge and follow up on the nf-test issue is my vote. |
Merged it, can you please open an issue with nf-test @nschcolnicov / @atrigila 👍🏻 |
@apeltzer askimed/nf-test#245, done! |
Addressing:
nf-core/modules#6189
#252
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).