Conversation
|
|
Since I've opted for conservative nf-test runs I'm running it manually to make sure we have full coverage. I’m running into a single, very simple assertion error for the utils_nextflow_pipeline subworkflow. This is after running nf-core submodules update as well. I've asked about it in the |
|
Ping @maxulysse |
Got confirmation from @mirpedrol it's an issue on the |
|
Awesome! I've tried to make some changes on my own repo to test it but I get this weird error in the ci 🤔 Is this something you've encountered yourself? |
|
I think we might want to run all the tests all the time actually: if you modify some files, run the test and they fail, and then do some other modifications that don't trigger the tests again, it will not run anything and still show a green mark, which may be misleading, see https://github.com/Aratz/seqinspector/actions/runs/11573281505/job/32215045767, I just wanted to reduce the number of shards to 2 but it didn't run the tests because modifying the ci file does not trigger the tests... |
There was a problem hiding this comment.
The ci.yml file runs the whole pipeline if I understand correctly.
I'd prefer to have them as separate GHA checks, if they do different things.
Fixed here nf-core/modules#6887 and applied in 3443734. All tests now pass on gitpod 🚀 |
Aratz
left a comment
There was a problem hiding this comment.
Great!
Just one thing is that now it's running the tests for the modules we're using, even though these are supposed to be validated in https://github.com/nf-core/modules/. I think for now it's fine but it might get very slow as we add more and more modules. Maybe we can look into how to restrict nf-test. I tried to look it up now but didn't manage to go anywhere...
PR checklist
[ ] If you've fixed a bug or added code that should be tested, add tests![ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs[ ] If necessary, also make a PR on the nf-core/seqinspector branch on the nf-core/test-datasets repository.nf-core lint).nf-test test main.nf.test -profile test,docker).[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).[ ] Usage Documentation indocs/usage.mdis updated.[ ] Output Documentation indocs/output.mdis updated.CHANGELOG.mdis updated.[] README.md` is updated (including new tool citations and authors/contributors).