-
Notifications
You must be signed in to change notification settings - Fork 205
Bump resolvers, hlint, brittany #1622
Conversation
|
@jneira I had to flush the cache on CircleCI for this to pass. Could the azure failures be something like that? |
|
Mmm some linux failed with i think i saw that error before, i've just rerun the failing jobs to see if it is transient |
|
Linux errors are gone, only left:
i would try both locally |
|
|
|
Ok. Heads up, I am rebasing this PR on the hie-bios update one, and some things are changing. We will see how it ends up. Aside, I had to blow away my cabal store and rebuild it, to get rid of weird errors about diamond deps. |
| @@ -1,39 +1,34 @@ | |||
| resolver: nightly-2019-09-21 # Last GHC 8.6.5 | |||
| resolver: nightly-2020-01-31 | |||
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.
We cant build hie with ghc-8.2.2, if we use it in stack.yaml we should remove it from azure ci.
I think the plan was keeping ghc-8.6.5 in stack.yaml until ghc-8.8.3 lands.
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.
Can we get azure to use stack-8.6.5.yaml instead? Which makes it clear
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.
mmm, there already is a job that uses stack-8.6.5.yaml. We can remove the one that uses stack.yaml
cabal now index state 2020-01-31T21:11:24Z GHC 8.8.2 is nightly-2020-01-31 GHC 8.6.5 is lts-14.22 hlint is 2.2.10 brittany is 0.12.1.1
|
Now, builds with ghc-8.4.3 are failing with: |
|
I am working to fix ghc-8.4.3 builds |
|
@jneira thanks |
cabal now index state 2020-01-31T21:11:24Z
GHC 8.8.2 is nightly-2020-01-31
GHC 8.6.5 is lts-14.22
hlint is 2.2.9
brittany is 0.12.1.1