-
Notifications
You must be signed in to change notification settings - Fork 10
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
Move nf-test files and container definitions #15
Conversation
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.
Stuff for future discussions I wanted to write down while I was looking at it, but nothing wrong with the code itself.
nextflow.config
Outdated
@@ -58,7 +58,7 @@ profiles { | |||
wave { | |||
wave.enabled = true | |||
wave.strategy = ['conda'] |
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.
If you change this to ['conda', 'container', 'dockerfile', 'spack']
it will use these in that order, so a user could use Wave to copy the existing container without rebuilding.
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.
Makes sense. You want to push that change?
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.
Just checked and there are lots of errors here about missing files and invalid tests.
No .nf-tests triggered? |
Why the move of the test file? This was a top-level 'pipeline' test (patterned after https://github.com/nf-core/fetchngs/blob/master/tests/main.nf.test etc). The move changes which main.nf is referenced, so there may be other changes to make, no? |
Moved pipeline level test back re: #14 (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.
It's perfect because I wrote most of it.
Ok. Tidied things up a little. Things left to do that be good to sort out before the release.
What else was left @pinin4fjords ? |
Subworkflow test? I'll get on the workflow one anyway |
MultiQC module groundwork:
|
This reverts commit 2475194.
We seem to be skipping tests fairly frequently leading to false positive results. I've added it as an issue: #16 For now, be careful when accepting a PR and make sure it's ran all tests. |
Ahh yes, sorry, this was me, and you're right, the strategy makes no sense 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.
Don't merge yet, mucking about with the tags
db3a957
to
13e6b4b
Compare
Co-authored-by: Adam Talbot <12817534+adamrtalbot@users.noreply.github.com>
container.config
and moved container definition back into processnextflow.config
files