You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Implement kevm.forgetBranch cheatcode (#899)
* draft FOUNDRYSemantics
* forgetBranch
* add mlEqualsTrue
* minor corrections
* add simplification step
* formatting
* add back not equal
* rename FOUNDRYSemantics to KontrolSemantics
* checking for negation as well
* correcting indentation
* expanding functionality
* heuristic simplifications
* further refinement
* refactoring _exec_forget_custom_step
* add show test
* fix test
* update expected output
---------
Co-authored-by: Petar Maksimovic <[email protected]>
Co-authored-by: Palina <[email protected]>
Co-authored-by: Petar Maksimović <[email protected]>
* Update dependency: deps/kevm_release (#940)
* deps/kevm_release: Set Version 1.0.780
* Sync Poetry files: kevm-pyk version 1.0.780
* flake.{nix,lock}: update Nix derivations
---------
Co-authored-by: devops <[email protected]>
* Build Custom Kontrol Versions using a workflow (#941)
* new file: .github/workflows/kup-build-kontrol.yml
- Adding a new feature to build kontrol images using kup and --overrides
* Update .github/workflows/kup-build-kontrol.yml
Co-authored-by: Everett Hildenbrandt <[email protected]>
* modified: .github/workflows/docker-push.yml
modified: .github/workflows/kup-build-kontrol.yml
- Standardizing the naming between these two workflows to know which is
for which
- Docker-push builds a custom version of kontrol with fixed dependencies
already published and built with kontrol
- kup-build-kontrol.yml will build the existing kontrol code with a
single new
dependency
modified: README.md
- Adding some readme instructions.
* renamed: .github/workflows/docker-push.yml -> .github/workflows/kontrol-push-fixed-deps.yml
renamed: .github/workflows/kup-build-kontrol.yml -> .github/workflows/kontrol-push-unfixed-deps.yml
modified: README.md
- Add some background between the two kontrol build workflows
* modified: README.md
-- Adding content to explain the two custom kontrol build workflows
* Update README.md
Co-authored-by: Anton Savienko <[email protected]>
* Filling in the 'get' placeholder with functionality to fetch appropriate
defaults when nothing is provided
* modified: README.md
- Adding instructions to fetch hash and use the wrofklow with multiple
dep options now available
* Update spelling and gramar
* modified: .github/workflows/kontrol-push-unfixed-deps.yml
- Fixing reporting of final versions used to build kontrol.
- Removing dfining override for undefined inputs to the workflow
---------
Co-authored-by: Everett Hildenbrandt <[email protected]>
Co-authored-by: Anton Savienko <[email protected]>
---------
Co-authored-by: Andrei Văcaru <[email protected]>
Co-authored-by: Petar Maksimovic <[email protected]>
Co-authored-by: Palina <[email protected]>
Co-authored-by: Petar Maksimović <[email protected]>
Co-authored-by: rv-jenkins <[email protected]>
Co-authored-by: devops <[email protected]>
Co-authored-by: Freeman <[email protected]>
Co-authored-by: Everett Hildenbrandt <[email protected]>
Co-authored-by: Anton Savienko <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+76-1Lines changed: 76 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,82 @@ To update the expected output of the tests, use the `--update-expected-output` f
71
71
make cov-integration TEST_ARGS="--numprocesses=8 --update-expected-output"
72
72
```
73
73
74
-
For interactive use, spawn a shell with `poetry shell` (after `poetry install`), then run an interpreter.
74
+
### Build Development Kontrol Image with Fixed Upstream Dependencies
75
+
--------------------------------
76
+
Relevant to this workflow [kontrol-push-fixed-deps.yml](.github/workflows/kontrol-push-fixed-deps.yml)
77
+
>This is relevant for internal development to publish development images of Kontrol with modified Kontrol changes and retain fixed upstream dependencies.
78
+
The use case for this workflow is intended to facilitate testing changes to Kontrol needed for use in testing CI or in other downstream workflows without needing to publish changes or PRs first.
79
+
80
+
The intent is to reduce the friction of needing custom builds and avoiding lengthy upstream changes and PRs.
81
+
82
+
### Build Kontrol with Kup and Specific Dependency Overrides
83
+
--------------------------------
84
+
Relevant to this workflow [kup-build-kontrol.yml](.github/workflows/kontrol-push-unfixed-deps.yml)
85
+
> This is relevant for internal development to publish development images of Kontrol for use in KaaS or a dockerized test environment.
86
+
Use the workflow [Kup Build Kontrol](.github/workflows/kup-build-kontrol.yml) to publish a custom version of Kontrol for use in CI and [KaaS](https://kaas.runtimeverification.com/).
87
+
[See KUP docs for more information](https://github.com/runtimeverification/kup/blob/master/src/kup/install-help.md#kup-install----override)
88
+
89
+
#### Using Kup
90
+
-------------
91
+
Relevant dependency options are shown below and can be listed using `kup list kontrol --inputs`
> **Notice**: the 'follows' in the 'kup list' output. This shows the links to the important dependencies and which are affected when you set the overrides.
118
+
119
+
Now run a build using kup and specific dependency overrides:
120
+
121
+
`kup install kontrol --override kevm/k-framework/haskell-backend "hash/branch_name" --override kevm/k-framework/haskell-backend "hash"`
122
+
123
+
> **Note**: It's important that you use the short-rev hash or the long for specific revisions of the dependencies to modify.
124
+
125
+
#### Using the workflow to publish to ghcr.io/runtimeverification
126
+
--------------------------------
127
+
128
+
#### Running the workflow
129
+
- Go to repo [Kontrol Actions Page](https://github.com/runtimeverification/kontrol/actions)
130
+
- Click on "Push Kontrol w/ Dependencies" from the left hand list
131
+
- Click on "Run Workflow" on the top right corner of the list of workflow runs is an option "Run Workflow".
132
+
- Use the 'master' branch unless you're doing something special.
133
+
- Input the override hash strings for specific dependencies to override in kontrol. See below on how to find the hash for the dependency.
134
+
- Then click "Run Workflow" and a job will start.
135
+
- The workflow summary shows the name of the image that was built and pushed e.g. ghcr.io/runtimeverification/kontrol-custom:tag
136
+
137
+
> **Note**: The tag will be a randomly generated string.
138
+
139
+
[The workflow](.github/workflows/kontrol-push-unfixed-deps.yml) takes multiple inputs to override the various components of kontrol. Those overrides are listed above in the example output of 'kup list kontrol --inputs'
140
+
141
+
To set the desired revisions of the dependencies. Find the associated hash on the branch and commit made to be used for the dependnecy override.
142
+
If an input is left blank, the workflow will workout the default hash to use based on kontrols latest release.
143
+
144
+
Example to fetch the desired hash to insert a different dependency version into the kontrol build.
145
+
Substitude the k-framework revision used to build kontrol.
0 commit comments