Create conda-fail.yml on Conda CI failures
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
okay, please expand this in the todo, so people can figure out what it means 🙂
Originally posted by @mashehu in https://github.com/nf-core/modules/pull/6286#discussion_r1846895317
Slack thread mentioned: https://nfcore.slack.com/archives/CJRH30T6V/p1724521923046009?thread_ts=1724406283.145319&cid=CJRH30T6V
Looking to add a file to the module if the conda-ci is failing and then we can skip the test. I also think https://github.com/askimed/nf-test/issues/260 is what we really need.
Example failure in Bioconda: https://github.com/bioconda/bioconda-recipes/blob/master/recipes/rsem/build_failure.osx-64.yaml
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 reviewing the proposed conda-fail.yml behavior, the Bioconda rsem build_failure.osx-64.yaml example, and nf-test issue 260. Clarify how a Conda CI failure should create and consume the file so the affected test can be skipped; done means the behavior is defined and works for the described failure case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100