Any ways to test a GHC build against large set of packages (including test suites)?

Ben Gamari ben at smart-cactus.org
Thu Jul 25 16:01:47 UTC 2019


Gert-Jan Bottu <gertjan.bottu at kuleuven.be> writes:

> Hi,
>
> I'm trying to do something similar : I'm hacking around with GHC, and 
> would like to build a large set of packages to verify my changes. 
> Similarly to the steps described below, I've followed the scheduled 
> build in .circle/config.yml, but I can't figure out how to force it to 
> use my own (hacked upon) GHC build?
>
I can't comment on stackage-curator but would second mpickering's
question. head.hackage is designed precisely for this sort of
application. I have a pair of draft blog posts [1,2], to be published
soon, which document its usage.

Cheers,

- Ben



[1] https://gitlab.haskell.org/ghc/homepage/merge_requests/16
[2] https://gitlab.haskell.org/ghc/homepage/merge_requests/29
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20190725/5895eaf7/attachment.sig>


More information about the ghc-devs mailing list