runtimeverification / runtimeverification/haskell-backend
Adjustments to CI
Open
Nobody has claimed this yet.
devops
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
As per thread: https://runtimeverification.slack.com/archives/CC360GUTG/p1648673575711919
- Should not run Integration Tests on GitHub provided runners, which provide very few VCPUs. Perhaps move to self-hosted runners: https://github.com/runtimeverification/devops/issues/46
- Quiet down the performance measurements, not needed for every commit.
- Why do integration tests start so late? Can they start at the same time as unit tests?
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 reviewing the repository's GitHub Actions configuration, then read the referenced Slack thread and runtimeverification/devops issue #46 for context. Done means integration tests no longer use GitHub-provided runners, performance measurements run less often, and integration tests can start alongside unit tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100