-
Notifications
You must be signed in to change notification settings - Fork 205
Conversation
looks reasonable to me |
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 also started working on supporting ghc 8.8.3, and only then I noticed there's already a PR. So, just a tiny comment here.
stack-8.8.3.yaml
Outdated
# To avoid build error with ghc-8.8.2 | ||
# See https://github.com/haskell/haddock/issues/1123 | ||
- git: https://github.com/haskell/haddock.git | ||
commit: be8b02c4e3cffe7d45b3dad0a0f071d35a274d65 | ||
subdirs: | ||
- haddock-api | ||
# - haddock-api-2.23.0 |
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.
Looks like - haddock-api-2.23.1
would also work — it seems to build with ghc 8.8.2 and later. Dunno if using a released version is preferable.
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.
Absolutely! Thanks for pointing it out
@jneira I noticed that at least one of the failed CI jobs (https://circleci.com/gh/jneira/haskell-ide-engine/4298?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) failed in Hoogle DB build on unsuccessful attempt to retrieve Some time ago, trying to use I did not examine all of the CI failures - but if they all break on retrieving |
Thank for take a look. They are transient erros related with connectivity of ci machines and are relatively frequent, but usually they go if you run the job again. |
I see, thanks. Yeah, on that level I'm incompetent to help, alas. Offhand, could you check if the problems are only with Stack-driven tests? |
Executing the tests locally with cradle:
cabal: for the testdata since my stack installation has been wiped and I didnt want to run it right now, but I guess I have to :( |
Once that @fendor has done the hard part (as usual 😸 ), fix the test suite, only left some errors in azure for windows: https://dev.azure.com/jneira/haskell-ide-engine/_build/results?buildId=744&view=results |
I am afraid that ghc-8.8.3 is throwing segfaults in azure ci, probably due to a ghc bug: https://gitlab.haskell.org/ghc/ghc/issues/17926 |
Should we still merge? |
6238a49
to
c3579bf
Compare
@fendor i think it can be merged, i am only trying to fix azure builds, although some errors are not related with ghc-8.8.3. |
Well, linux stack jobs have ran out of disk space since c8ed3e5 :
It make the download of ghc-8.8.1, necessary for wrapper-tests fail:
It is not related with this pr, so i would merge this if other builds are succesful. |
Almost all failing jobs are due to #1729 so i think it can be merged |
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.
LGTM!
Hopefully we can fix the CI in a follow up PR.
Uh oh!
There was an error while loading. Please reload this page.