Address limitations of using nf-test sharding
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
List post #6286 that aren't breaking but would be nice to have
### Tasks
- [ ] Functioning Test Report
- [ ] Smart number of shards
- [ ] Avoid failing conda tests
- [ ] Add branch checks for CI jobs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading post #6286 and the four unchecked tasks: test reporting, shard sizing, conda-test failures, and branch checks for CI jobs. Done means the relevant nf-test sharding limitations are addressed without breaking the existing workflow, with each task demonstrably functioning.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100