-
Notifications
You must be signed in to change notification settings - Fork 143
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
Dev -> Master 2.7.0 #420
base: master
Are you sure you want to change the base?
Dev -> Master 2.7.0 #420
Conversation
post-release dev bump version and snapshots
add missing comma
Important! Template update for nf-core/tools v2.12
Fix/samplename join
Following the template
Important! Template update for nf-core/tools v2.13
Important! Template update for nf-core/tools v2.13.1
Samplesheet input section was duplicated
remove duplicate section from usage.md
This should now have both unique samples and samples that need to be merged for both single-end and paired-end scenarios.
Switching R1 and R2 round for the last test merge, which should also work (both for merging and for processing even though it won't align in directional mode).
update bismark+bwameth modules; sub-wf; wf
do not merge until confirmation of test_full runs |
udpate tests to use nft-bam for bam files
update SAMTOOLS_FAIDX fasta input after reorg
{ assert workflow.success }, | ||
{ assert snapshot( | ||
// Number of tasks | ||
workflow.trace.succeeded().size() | ||
).match() } |
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.
no snapshots of files?
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.
they are there...plz check again
https://github.com/nf-core/methylseq/blob/0b8372017fad8e7f8cdc65a63baa326381ce8d60/tests/default.nf.test.snap
{ assert workflow.success }, | ||
{ assert snapshot( | ||
// Number of tasks | ||
workflow.trace.succeeded().size() | ||
).match() } |
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.
no snapshots of files?
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.
same
{ assert workflow.success }, | ||
{ assert snapshot( | ||
// Number of tasks | ||
workflow.trace.succeeded().size() | ||
).match() } |
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.
no snapshots of files?
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.
its there
|
||
// location of an optional nextflow.config file specific for executing tests | ||
configFile "nextflow.config" | ||
configFile "tests/nextflow.config" |
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.
what else do you have there that's not already in the profile test?
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.
thats how I have it -
Line 9 in 0b83720
configFile "tests/nextflow.config" |
how come you are seeing this diff ?
profile "test" | ||
|
||
// List of filenames or patterns that should be trigger a full test run | ||
triggers 'nextflow.config', 'nf-test.config', 'conf/test.config', 'conf/test_full.config' |
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.
no .nf files?
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 nf files are automatically detected by nf-test with the --changed-since
feature in the CI
the triggers here meanwhile will make sure all tests are run if any of the trigger files are 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.
Some minor comments.
Looking super good
apply code review suggestions and activate igenomes bwameth index use
No description provided.