Running validation tests and CI
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 409
- PR merge metrics
- No merged PRs in 30d
Description
What tests are run during submission in CI and how do we test changes before submission?
Also, the CI missed this compilation issue [1], because Windows on Arm was not tested. Now that Github are available with WoA runners, could we add them to the project?
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 project's CI configuration and the tests run during submission, then compare the missed compilation issue described in PR #289. Determine how changes are tested before submission and what is needed to add Windows on Arm GitHub runners; done means the workflow covers WoA and the testing process is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, github-actions
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100