Hi Ben, I was wondering why my pull request (merely to trigger a bit more of CI than what I have at my local disposal) was suddenly failing (1), when it worked in a previous incarnation (2).
It turns out that either CI or the entire tree is broken since (3) being the last sound one. Looks like x86-64 is affected on the linux platform only. Darwin seems to work, i386 too, and my PR (2) has been validated for PPC64le recently. So this is just a heads up that there is something fishy with github->CircleCI (at least). Cheers, Gabor (1) https://circleci.com/gh/ghc/ghc/tree/pull/242 (2) https://circleci.com/gh/ghc/ghc/tree/pull/224 (3) https://circleci.com/gh/ghc/ghc/tree/pull/239 On 12/21/18, Ben Gamari <b...@smart-cactus.org> wrote: > Ara Adkins <m...@ara.io> writes: > >> Hey All, >> >> Sorry for my confusion, but I'm a bit unclear as to when we're meant to >> start working against the GHC repo on the gitlab.haskell.org instance. I >> had in mind that the cutover was intended to be the 18th, but going on >> there it still appears as if it's mirrored from git.haskell.org. Can >> somebody clarify this for me? >> > Sorry for the confusion. I have been reluctant to formally announce the > cut-over until CI is green but this has taken a fair bit longer than > anticipated due to the long CI cycle time. Nevertheless people have > started submitting MRs against the GitLab instance and you are more than > welcome to do so. > > As far as the official upstream repository, indeed > gitlab.haskell.org/ghc/ghc is still mirroring git.haskell.org/ghc. This > will change when I formally announce the switchover. > > Cheers, > > - Ben > > _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs