runtimeverification / runtimeverification/kontrol
CI runner failures
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
As suggested by @ehildenb, this issue is meant to track issues with our CI jobs for investigation and monitoring.
One recent example of such problem is seven consistent failures of booster or legacy integration tests CI jobs on a Kontrol PR, each failing with pyk.kore.rpc.JsonRpcError: Smt solver error: https://github.com/runtimeverification/kontrol/actions/runs/7771577139/job/21217231198?pr=330, reported by @anvacaru.
All CI jobs passed once the GitHub runner has changed: https://github.com/runtimeverification/kontrol/actions/runs/7771577139?pr=330.
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 linked GitHub Actions run for PR 330, focusing on the booster and legacy integration jobs that reported pyk.kore.rpc.JsonRpcError: Smt solver error. Compare the failed run with the successful run after the GitHub runner changed; the issue is done when the CI failure has been investigated and the findings are recorded for ongoing monitoring.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100