[GHC DevOps Group] CI status update and questions

[Ben Gamari]

Facundo Domínguez <facundo.dominguez at tweag.io> writes:

> Hello,
>
> Increasing the amount of threads in circleci brings the builds+tests
> near to 2.5 hours. We don't need to split the build in CircleCI. Now
> we need to fix the failing tests.
>
> Appveyor is more limited. We can build the compiler with the quick
> flavor within the 90 minutes. Is this enough, or do we really need to
> build an optimized compiler?
>
If we are going to use our CI infrastructure to build binary
distributions then it is necessary to build an optimized compiler.
Moreover, I would be quite weary of running our usual CI in anything
other than the configuration which it will be deployed in.

> Second question: should appveyor run all the tests that we already run
> in circleci?
>
Yes. A large part of the motivation of this rework is to improve our CI
coverage. Unfortunately, compilers are notoriously environment-sensitive
(see, for instance, #14675) so taking short-cuts here would be quite
harmful to that goal.

Cheers,

- Ben
-------------- 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-devops-group/attachments/20180216/90e23f15/attachment.sig>