Conversation
|
Due to the long runtime of this test, I decided to move it to the EVA cluster, but I cannot get FastQC to run successfully there :/ Here's the error for future reference: I tried increasing the memory of FastQC, and decreasing the number of cores (the module does a memory/cores division to keep Java in check), but to no avail. |
|
Update. It seems that the process resources specified in the Sadly, there is no way to tweak the profile order in nf-test: https://www.nf-test.com/docs/configuration/#managing-profiles I tried adding |
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.3.2. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
Running anotehr test locally on eva cluster now |
|
@nf-core-bot fix linting |
|
|
The GH runner runs out of storage space at the adapter trimming step, and thus the job fails. I'm not sure how we could fix that. I guess this test could simply be a non-CI test (since it's the one used for benchmarking), and we accept it fails on GH? @jfy133 thoughts? |
Well that's because you're tryign to run
|
|
snapshto for test_full is for manual testing prior release |
Closes #1141
PR checklist
scrape_software_versions.pynf-core lint .).nextflow run . -profile test,docker).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).