Cachix workaround & push kevm to k-framework-binary cachix#2841
Merged
automergerpr-permission-manager[bot] merged 4 commits intomasterfrom Apr 22, 2026
Merged
Cachix workaround & push kevm to k-framework-binary cachix#2841automergerpr-permission-manager[bot] merged 4 commits intomasterfrom
k-framework-binary cachix#2841automergerpr-permission-manager[bot] merged 4 commits intomasterfrom
Conversation
anvacaru
approved these changes
Apr 22, 2026
0640b39
into
master
33 of 36 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The kevm release workflow is failing when pushing to
k-frameworkcachix using the cachix tool with the known cachix server error: https://github.com/runtimeverification/evm-semantics/actions/runs/24573697176/job/71853373954This PR works around this by failing silently when pushing to that cache.
On top of that, apparently, the evm-semantics repository was not pushing and pinning
kevmin thek-framework-binarycachix cache, which contains the binary builds of kevm. Therefore, I added a release workflow for that as well, including the workaround code that checks manually whether the push to cachix was successfully, as was added in other repositories as well.Finally, I noticed that the release workflow tests KEVM even though this is already done in the test PR workflows. Henceforth, I removed this test from the release workflow as I wanted to keep the nix-cache and the new nix-binary-cache workflows consistent and similar without adding duplicated kevm testing effort.