Closed taylorreiter closed 1 year ago
nf-core lint
overall result: Passed :white_check_mark: :warning:Posted for pipeline commit d0351a5
+| ✅ 125 tests passed |+
#| ❔ 21 tests were ignored |#
!| ❗ 5 tests had warnings |!
well -- CI is going to fail bc multiqc doesn't have a conda package bc the sourmash modules haven't been merged yet. sighhhh
Edit: I decided to enable conda from an earlier version because we're releasing this as a pub soon, and I want tests to be passing/the pipeline to be functional/all the juicy stuff on the master branch when we do that.
Do I need to re-review this or is there a different PR with these updates?
re-review please! the first time you reviewed it was failing all of its tests
FastQC keeps failing for some of the long reads, either with not enough time or OOM. I think enabling retries and scaling resources with the attempt number should fix this.
Edit: adding details requested by @elizabethmcd on nf-core/conda: In december, nf-core switched how conda packages are declared at the top of modules. This coincided with a nextflow version bump. if you don’t bump your nextflow but do change your conda declarations, docker profiles fail to run. At first this was only failing on CI for me, not locally, because conda updates the nextflow version automatically if you bump the version on nf-core tools. but to switch the nextflow version in CI, you not only need to change it in the github workflow but also in the README and the nextflow config