-
-
Notifications
You must be signed in to change notification settings - Fork 389
stack CI: switch to offic. haskell images, bump to lts-22.9 (ghc 9.6.4) #4060
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
Conversation
@@ -20,25 +20,12 @@ extra-deps: | |||
- retrie-1.2.2 | |||
- hiedb-0.5.0.1 | |||
- implicit-hie-0.1.4.0 | |||
- hie-bios-0.13.1 |
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.
Removing these from extra-deps, because all of these are in lts-22.9
7c9b7cc
to
07d4ef5
Compare
@@ -76,19 +60,22 @@ defaults: &defaults | |||
version: 2 | |||
jobs: | |||
stackage-lts21: | |||
docker: |
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.
Switching to official haskell images.
They already have latest stack installed and setup + specific version of ghc (corresponding to image tag) preinstalled. That means no need to have separate stack upgrade and stack setup steps.
Also ghc is installed in separate location, which means smaller CI caches since we're caching ~/.stack folder (so cache is about 1GB smaller because we don't have to cache GHC installation within ~/.stack)
Motivation:
this week I saw several instances of stack CI jobs failing with errors ala "failed to download stack binaries from fpcomplete servers".
I propose we switch to official haskell images which have latest stack preinstalled so we can avoid this class of failures altogether.