Skip to content
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

Update Haskell package set to LTS 15.11 (plus other fixes) #86961

Merged
merged 14 commits into from May 8, 2020
Merged

Conversation

peti
Copy link
Member

@peti peti commented May 5, 2020

This PR is test-built by Hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. I'll fix up the remaining errors and merge it on Friday, 2020-05-08 20:00 CET. You can watch this live on Twitch at https://www.twitch.tv/peti343. In addition to the chat features offered by Twitch, there is also a voice conference at https://discord.gg/YTEa3XR that viewers can use to chat with me and with each other.

TODO

peti and others added 7 commits May 8, 2020 21:11
This is the haskell-updates version of #86659
This update was generated by hackage2nix v2.15.3-1-gb7c82db from Hackage revision
commercialhaskell/all-cabal-hashes@78f6cea.
As of releaser 3.0.0 the build does not fail anymore.
hlint 3.0 is shiny and new and is very picky in its dependencies.
@peti peti merged commit effa374 into master May 8, 2020
@peti
Copy link
Member Author

peti commented May 14, 2020

Next week, we'll merge #87805.

@expipiplus1
Copy link
Contributor

expipiplus1 commented May 17, 2020

Hi @peti, ccb81f5 seems to have a very negative effect on building haskell packages on my machine. I frequently see loads of 100+, on a 8 core (16 virtual, Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz) machine. I've not done any detailed benchmarking but this can't be good. Do you have a script I can run to generate some compile times on my machine?

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants