-
Notifications
You must be signed in to change notification settings - Fork 651
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
Get Singularity CI tests working #143
Conversation
27526d6
to
9b45441
Compare
This reverts commit 9b45441.
….yml" This reverts commit ffc218e.
This will cause a bit of duplication, but it appears to work. Still the same logic, because any changes to bowtie*/build will run the align modules also. So the bowtie_align tags may not even be necessary, since we can't seem to get the bowtie*_build tags to kick off on their own anyways. Thank you for coming to my TED talk.
de4a513
to
d48e865
Compare
c888116
to
d48e865
Compare
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.
Looks good just a few questions basically.
The singularity version necessary I guess?
md5sum: a23e9a2a76e949aeb3693bcfae41a615 | ||
md5sum: a81cb18024616415a6cec3108a36fccd |
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.
Any idea why this changed?
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.
# reads processed: 10000
# reads with at least one alignment: 2 (0.02%)
# reads that failed to align: 9998 (99.98%)
Reported 2 alignments
This is the latest version which is only showing 2 alignments...are you able to run pytest
via the old tests so we can see the difference?
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.
The old version generated the output below which is why the tests are failing:
# reads processed: 10000
# reads with at least one alignment: 1 (0.01%)
# reads that failed to align: 9999 (99.99%)
Reported 1 paired-end alignments
I guess this highlights the importance of using seed values where possible in main.nf
for the tests to always generate the same alignments and not by random. At least, this is what I think is happening here.
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! I think we should create a separate issue for why we had to change the md5sum
for bowtie align
and come back to that so we can get this in to start figuring out how to deal with Conda!
💥 |
Should fix issues with singularity builds #145 and "fixes" the
bowtie*_build
tags not running.