Run tests and examples that use optional components on GitHub
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
External programs upon which cached example output depends should probably be installed as part of our github workflow, so we can test those examples regularly. Those programs include phcpack, bertini, qepcad, bergman, and polymake.
Originally posted by @DanGrayson in https://github.com/Macaulay2/M2/issues/1953#issuecomment-783471096
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
Start by locating the GitHub workflow that runs examples and identify how cached example output is tested. Determine how phcpack, bertini, qepcad, bergman, and polymake can be installed in that workflow; done means those optional-component examples run regularly in GitHub checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100