Nix use clash-compiler GHC version #29
Conversation
|
@martijnbastiaan CI seems to be failing over signatures, any clue as to why/how that works? |
|
No clue... If I'm to hazard a guess it's a temporary failure. Try again tomorrow? 🫠 |
jaschutte
force-pushed
the
master
branch
2 times, most recently
from
2336df9 to
e2e7d07
Compare
|
The issue had to do with The upstream bug report: haskell-actions/setup#122 |
.github/workflows/ci.yml
Outdated
| matrix: | ||
| os: [ubuntu-latest] | ||
| cabal: ["3.6"] | ||
| cabal: ["3.16"] |
There was a problem hiding this comment.
Is it possible to just drop cabal entirely? I trust the action to figure out the right Cabal version.
There was a problem hiding this comment.
I'm not familiar enough with how github CI works to know what "dropping" exactly means hehe. I can set it to latest which would just follow the latest supported version of the Cabal. I think that would achieve the same goal.
There was a problem hiding this comment.
Yeah that should work :)
Rather than use a predefined local version of GHC, use the same version the clash compiler uses. This makes it so the flake doesn't have to get independently updated and can just follow whatever clash-compiler has. It also updates the cabal version of CI to a supported release. Cabal 3.6 supported was dropped ??? ago and it broke CI.
2 participants
Rather than use a predefined local version of GHC, use the same version the clash compiler uses. This makes it so the flake doesn't have to get independently updated and can just follow whatever clash-compiler has.
This change has been made to following the decision to pin clash-compiler to a minor version of GHC. Changing minor versions for each project depending on clash-compiler will be tedious, so this will make it automatically follow the same version of clash-compiler.
Marked as draft until clash-lang/clash-compiler#2984 is merged.
TODO: