-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modified: .github/workflows/release.yml #4093
modified: .github/workflows/release.yml #4093
Conversation
modified: .github/workflows/test.yml - Update nix release process for test/release workflows - Publish release builds to k-framework-binar - Publish iterative CI builds to k-framework. - Reduce build times upstream and in CI PR testing. - Supporting issue of haskell-backend components being built upstream by dependents.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have insight into our cachix setup so I cannot judge whether this solves our problem. OTOH it is certainly not harmful (unless the new github action starts to fail on us, see comment).
So from my side, it is OK to merge.
- name: Build | ||
run: nix build .#kore-exec .#kore-rpc-booster | ||
- name: 'Build and Cache' | ||
uses: workflow/nix-shell-action@v3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to introduce an error message unrecognised flag '-c'
(cannot possibly come from the commands below, and happens before any build output is printed). Is this action stable/recommended by people?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's the same logic / version we use in Kontrol
https://github.com/runtimeverification/kontrol/blob/master/.github/workflows/release.yml#L45
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which looks like also produces the same error. Not sure when this was introduced though without looking at git history seems it didn't raise any flags though. I'll spend a minute on it see if there' and a similar error is thrown on linux as well.
- Undo the change to build and push to cachxi publish repo on every PR build. - This is handled lower down inherently by the cachix action for just linux.
modified: .github/workflows/test.yml
dependents.