-
Notifications
You must be signed in to change notification settings - Fork 741
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
New kma module #7251
base: master
Are you sure you want to change the base?
New kma module #7251
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.
Looks very good already. You are missing the snapshot. Can you run
nf-core modules test kma/kma
and push the .snap file?
Thanks for reviewing! nf-test is still WIP. In fact, I need my KMA_INDEX module merged to nf-core first in order to test the KMA_KMA module because I'd like to avoid pushing tool-specific testdata to nf-core. I am aiming for a nf-test similar to |
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.
one stylistic hint and a question about the module folder structure
Thanks @mazzalab , good catch about the Harshil Alignment style. Even though it hurts my eyes 😉 I'll adhere to the style with the next fix. |
Error: nf-test produces no output
My goal is to reproduce the same logic as with the nf-tests of bwa index and bwa mem (see here for comparison), i.e. the test is supposed to create an index with the nf-core/kma/index module and the test the kma/kma alignment module. 🚧 What I investigated so far:
❓ Has anyone a clue or pointer what is going on here? Where should I continue to investigate? Any help much appreciated. |
Hi @jfy133 , cc @MarieLataretu , GitHub CI: Local: Gitpod: This suggests that there is something going on with the docker container, right? The screenshots attached are from gitpod. For conda and singularity outputs I even checked the files manually and it's all correct. The error using docker (on gitpod) is the same you posted above. |
It is jus the sarscov - fasta and the sarscov - fasta - matrix tests which are failing. Test [726e4ada] 'sarscov2 - fasta - sparse'
> Nextflow 24.10.3 is available - Please consider updating your version to it
> N E X T F L O W ~ version 24.10.2
> Launching `/home/runner/work/modules/modules/.nf-test-726e4ada36f370274ea46e18c45b05ca.nf` [sharp_pauling] DSL2 - revision: 3d9dd9af05
> WARN: Unknown directive `params` for process `KMA_INDEX`
> WARN: Unknown directive `params` for process `KMA_KMA`
> [c0/c5bf5b] Submitted process > KMA_INDEX (MT192765.1)
> [97/474896] Submitted process > KMA_KMA (nfcore_testsample)
PASSED (10.318s) works for example. @Krannich479 I would try a wave container and check if that works. We will swap to those anyway (I think). https://seqera.io/containers/ |
Exactly, @famosab it is only 2/6 tests failing. That's two too many though :) |
Dear @famosab, |
use wave container if docker is engine
a3bd776 was my attempt to use this wave container. In Gitpod, the |
When I run it locally everything works: nf-core-3.1 famke@Famkes-MacBook-Air ~/Desktop/nf-core-modules kma_kma ± nf-core modules test kma/kma --profile docker -u [11:17AM]
,--./,-.
___ __ __ __ ___ /,-._.--~\
|\ | |__ __ / ` / \ |__) |__ } {
| \| | \__, \__/ | \ |___ \`-._,-`-,
`._,._,'
nf-core/tools version 3.1.1 - https://nf-co.re
There is a new version of nf-core/tools available! (3.1.2)
INFO Generating nf-test snapshot
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── nf-test output ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 🚀 nf-test 0.9.2 │
│ https://www.nf-test.com │
│ (c) 2021 - 2024 Lukas Forer and Sebastian Schoenherr │
│ │
│ Load .nf-test/plugins/nft-bam/0.5.0/nft-bam-0.5.0.jar │
│ Load .nf-test/plugins/nft-compress/0.1.0/nft-compress-0.1.0.jar │
│ Load .nf-test/plugins/nft-vcf/1.0.7/nft-vcf-1.0.7.jar │
│ Warning: every snapshot that fails during this test run is re-record. │
│ │
│ Test Process KMA_KMA │
│ │
│ Test [5f1111b2] 'sarscov2 - fasta - sparse' PASSED (6.179s) │
│ Test [aa06bd01] 'sarscov2 - fasta - sparse - stub' PASSED (6.601s) │
│ Test [6997155d] 'sarscov2 - fasta' PASSED (6.623s) │
│ Test [866eb651] 'sarscov2 - fasta - stub' PASSED (5.553s) │
│ Test [48ec76fa] 'sarscov2 - fasta - matrix' PASSED (6.075s) │
│ Test [6bfbba61] 'sarscov2 - fasta - matrix - stub' PASSED (6.385s) │
│ │
│ │
│ SUCCESS: Executed 6 tests in 37.461s │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
INFO Generating nf-test snapshot again to check stability
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── nf-test output ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 🚀 nf-test 0.9.2 │
│ https://www.nf-test.com │
│ (c) 2021 - 2024 Lukas Forer and Sebastian Schoenherr │
│ │
│ Load .nf-test/plugins/nft-bam/0.5.0/nft-bam-0.5.0.jar │
│ Load .nf-test/plugins/nft-compress/0.1.0/nft-compress-0.1.0.jar │
│ Load .nf-test/plugins/nft-vcf/1.0.7/nft-vcf-1.0.7.jar │
│ │
│ Test Process KMA_KMA │
│ │
│ Test [5f1111b2] 'sarscov2 - fasta - sparse' PASSED (7.046s) │
│ Test [aa06bd01] 'sarscov2 - fasta - sparse - stub' PASSED (6.746s) │
│ Test [6997155d] 'sarscov2 - fasta' PASSED (6.048s) │
│ Test [866eb651] 'sarscov2 - fasta - stub' PASSED (6.199s) │
│ Test [48ec76fa] 'sarscov2 - fasta - matrix' PASSED (7.007s) │
│ Test [6bfbba61] 'sarscov2 - fasta - matrix - stub' PASSED (6.495s) │
│ │
│ │
│ SUCCESS: Executed 6 tests in 39.596s │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
INFO All tests passed! I changed the nf test file a little though. |
Module works now according to nf-tests
The secret ingredient is to rerun the tests in Github CI until it works for some reason.... |
Sorry to disappoint but to me it seems like the nf-test is not run at all now 👀 @mashehu Are there recent changes that stopped the runners or something? |
hmm, something strange going on in the nf-test detection https://github.com/nf-core/modules/actions/runs/12884972870/job/35931026117?pr=7251#step:7:80 |
fix is here: #7340 |
I think the issue is related to this warning: WARNING: Your kernel does not support CPU shares or the cgroup is not mounted. Shares discarded. @mashehu Could that be related to the runners? (And thank you for the fix) |
nope that warning is a red herring (as it is just a warning and raised in all runs, not just failing ones). @sateeshperi any idea why docker throws a 95 status error here? |
PR checklist
Closes PR #7242
versions.yml
file.label
nf-core modules test <MODULE> --profile docker
nf-core modules test <MODULE> --profile singularity
nf-core modules test <MODULE> --profile conda