1. 14 Nov, 2019 3 commits
  2. 12 Nov, 2019 1 commit
    • Ryan Scott's avatar
      Remove some expected failures · 64a4f798
      Ryan Scott authored
      We can remove several packages from the expected failures list due
      to recent developments:
      
      * We can remove `hashtables`, `http2`, `statistics`, and
        `unicode-transforms` from the expected failures for 8.8 now that
        the fix for ghc#16288 has been backported to the `ghc-8.8`
        branch.
      * We can remove `singletons` and `vinyl` from the expected failures
        for `master` now that ghc!2102 has landed. The `vinyl-0.12.0`
        patch needs to be updated since it uses `TypeFamilyDependencies`
        in such a way that requires `UndecidableInstances`. (Note that
        `singletons` already enabled `UndecidableInstances` in all the
        right places, so no further action is required for that library.)
      64a4f798
  3. 11 Nov, 2019 1 commit
  4. 09 Nov, 2019 1 commit
    • Ryan Scott's avatar
      Update free patch, add patches for HEAD support · aea92517
      Ryan Scott authored
      The `free-5.1.2` patch has been updated to accommodate recent changes
      to unary `TupE` expressions in 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`
      aea92517
  5. 08 Nov, 2019 2 commits
    • Ben Gamari's avatar
      ci: Add README · ff84f213
      Ben Gamari authored
      ff84f213
    • Ben Gamari's avatar
      ci: Don't constrain to patched package versions · 4a714778
      Ben Gamari authored
      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.
      4a714778
  6. 07 Nov, 2019 5 commits
  7. 06 Nov, 2019 2 commits
  8. 05 Nov, 2019 11 commits
  9. 04 Nov, 2019 11 commits
  10. 31 Oct, 2019 1 commit
  11. 23 Oct, 2019 1 commit
  12. 22 Oct, 2019 1 commit