runtimeverification / runtimeverification/kontrol
Increasing the Kontrol test time limit on "integration tests (booster)"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
To Alleviate the false failure of tests due to time limit restrictions, it's suggested to increase the time limit of these tests.
One Example of this
https://github.com/runtimeverification/kontrol/actions/runs/10283080073/job/28526574497?pr=750
Likely more found in day to day PRs being run and failing due to this false test failure.
If this time limit is enforced by a requirement, then worth discussing if maybe test machine is set to use a 'fast' runner instead of a regular 'normal'. The trade off is a CPU with a higher clock speed, and the same amount of RAM.
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 with the GitHub Actions job named "integration tests (booster)" and inspect how its time limit and runner are configured. Use the linked Actions run as the failure reference; done means the relevant tests no longer fail falsely because of the enforced time limit, with any runner trade-off addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100