-
Notifications
You must be signed in to change notification settings - Fork 841
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
WIP: Bump resolver used in release.hs #5552
Conversation
I think the integration tests might be failing due to using an LTS that requires a different GHC version than is already available. Probably best to bump the integration tests to also use a consistent LTS. One of these days I might just drop the |
+1 from me on that happening ultimately, but agreed, no rush |
I'm in particular unable to fix up the Nix problems here. If someone else is interested in taking a crack at that, I'd really appreciate it. |
This also updates release.hs to use a more recent resolver, since otherwise we'll have trouble on ARM64 with conflicting LLVM installations. Unlike #5552, I took the simple workaround here of installing GHC 8.6.5 in addition to the more recent GHC needed by release.hs.
@snoyberg I've tried it out locally but couldn't reproduce, the error
means that there is no ghc8.10.4 in nixpkgs but it seems to be present in the latest |
I discovered the line in question here:
We locked it down previously to make the test suite reproducible. But I have no idea what we should bump it to instead. |
Oh, I completely forgot that it was pinned, sorry, will take a look |
This also updates release.hs to use a more recent resolver, since otherwise we'll have trouble on ARM64 with conflicting LLVM installations. Unlike #5552, I took the simple workaround here of installing GHC 8.6.5 in addition to the more recent GHC needed by release.hs.
FYI, I'm already including a workaround in this PR: It's not as good, since it still requires two GHCs to be installed, but it does work around using the older GHC for release.hs itself. |
@snoyberg it looks like we can't use the last stable version 20.09 as there's no 8.10.4 there:
but 21.05 is almost released so I guess this should be good enough as an option
but there's no channel for it yet so some other way of pinning is needed |
@snoyberg I guess using env vars in that test could be even more explicit and we'll have the same config both in CI and locally and it looks like
With the URL to set in the test |
Bump pantry version
Sanity check does not include GHC_PACKAGE_PATH
Update community links
…-release-resolver
Rather late in the day, I realised that this pull request was seeking to do part of what I am trying to do in pull request #5697 (move stack to lts-19.7/GHC 9.0.2) - but this request is for lts-8.10.4/lts-17.10. My GHC 9.0.2 pull request passes the unit tests, and the integration tests on Windows, but I am stuck with [1] the integration tests running on |
Note: Documentation fixes for https://docs.haskellstack.org/en/stable/ should target the "stable" branch, not master.
Please include the following checklist in your PR:
Please also shortly describe how you tested your change. Bonus points for added tests!