nf-core / nf-core/test-datasets
aws s3 links
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 164
- Forks
- 530
- Avg merge
- 7h 9m
- Merged PRs (30d)
- 48
Description
We currently have three modules that use a link to a s3 bucket (all to the same database)
./tests/modules/nf-core/amps/main.nf
./modules/nf-core/malt/build/tests/main.nf.test
./modules/nf-core/malt/run/tests/main.nf.test
These don't seem to currently work on the CI/CD, and so something needs doing to fix these.
Presumably we don't want them for the same reason as github links.
Contributor guide
No contributing guide indexed for this repository
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
Inspect the three named files: tests/modules/nf-core/amps/main.nf, modules/nf-core/malt/build/tests/main.nf.test, and modules/nf-core/malt/run/tests/main.nf.test. Start by reviewing how their S3 links are used and the linked nf-core/modules pull request. Done means the affected test data references no longer cause CI/CD failures and the chosen treatment is applied consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100