Add automated tests for various SCR builds
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 108
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
There are several different ways to build SCR, each with numerous configuration options. While it could be overkill to account for every possible combination, we should be sure it builds basic builds for each method (spack, CMake with separate components, CMake with release dist tarball).
We should also include specific build configurations that we know are important to key users.
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 existing build and CI entry points for Spack, CMake with separate components, and CMake using the release distribution tarball. Identify the basic build configurations and important key-user configurations that should be covered. Done means automated tests exercise the agreed configurations and report build failures clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cmake
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100