runtimeverification / runtimeverification/kontrol
Add CI job for output update
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Related: https://github.com/runtimeverification/evm-semantics/pull/1964
As suggested by @ehildenb and @PetarMax, we can make a "on-demand" CI job that can update expected outputs on a branch. That would solve the K version mis-matches. It could be triggered on a branch and then push the update to that branch. We would need to make sure not to abuse it, and actually inspect the updated output. That was previously done in KEVM https://github.com/runtimeverification/evm-semantics/pull/1964, so we should just adapt it to the current Kontrol and enable it.
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 related evm-semantics pull request 1964 to understand the earlier on-demand output-update CI workflow, then identify the corresponding CI configuration in Kontrol. Done means a branch-triggered job can update expected outputs and push them back to that branch, with the generated output inspected before use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100