More CI tests
Open
Nobody has claimed this yet.
RFC / discussion
testing
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Brainstorming. We now have a free container for the "more-tests".
We could add an MPI build (although only testing locally much like --fork).
Do we currently test a legacy build anywhere?
Anything else we should test? Perhaps running the Test Suite in -internal mode (disabling the few formats that give false positives)?
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
Review the existing CI setup for the more-tests container and compare it with local --fork testing. Investigate the proposed MPI build, legacy build coverage, and Test Suite -internal mode, then define which additions are selected and what successful CI results constitute completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100