This utilizes GitLab CI's `parallel`[1] field to divide the build into
several jobs, each handling a subset of the built packages. The job
count is a bit of a trade-off between build re-use and parallelism. I'm
trying 5 for now.

[1] https://docs.gitlab.com/ee/ci/yaml/#parallel

The `free-5.1.2` patch has been updated to accommodate recent changes
to unary `TupE` expressions in ghc/ghc@708c60aa.

The following new patches have been added:

* `fclabels-2.0.3.3`
* `free-algebras-0.0.8.0`
* `generics-sop-lens-0.2`
* `geniplate-mirror-0.7.6`
* `language-docker-8.0.2`
* `mustache-2.3.0` (based on https://github.com/JustusAdam/mustache/pull/42)
* `parameterized-utils-2.0.1.0`
* `persistent-sqlite-2.10.5`
* `row-types-0.3.0.0`
* `trivial-constraint-0.6.0.0`
* `typenums-0.1.2.1`
* `witness-0.4`

Previously we constrained the CI install plans to use only patched
versions of any packages for which we had patches. This was an attempt
to decouple ourselves from the evolution of Hackage a bit. Specifically,
I was worried that if we didn't constrain the install plan to the
patched versions then we would end up having spurious build failures
every time a new minor package version is released (since
cabal-install would prefer the new release over our patched
version). Admittedly this is just a hack to work around the fact
that version bounds are generally quite loose, but it seemed like a
reasonable trade-off at the time.

However, this ended up making it hard to support older major versions
of a package simultaneously with the newest version if the latter
doesn't require a patch. Let's try doing away with the constraints.

It will only confuse the reader.

Ben Gamari authored 5 years ago and Ben Gamari committed 5 years ago

This clamps the mtime of files in patched source tarballs to the mtime
of the patch to ensure that the time of the build doesn't sneak into the
hashes in the index.

These packages all have more recent Hackage versions that require
patching to support GHC HEAD.

Ben Gamari authored 5 years ago and Ben Gamari committed 5 years ago

This should fix #11.

Ryan Scott authored 5 years ago and Ben Gamari committed 5 years ago

Each of these libraries now has a newer Hackage release that compiles
with GHC 8.8/HEAD.

Now since we have support for expected-broken packages we needn't be as
cautious about linting.

This adds a `--expect-broken` option to the CI driver executable along
with a simple shell script containing the list of packages which we
expect to fail for a given GHC version.

See ghc/ghc#17371