: ghc-devs@haskell.org
Betreff: Re: Near-daily "Remote mirror update failed" e-mails from GitLab
Ryan Scott writes:
> Almost every day now I receive an e-mail from GitLab titled "Remote
> mirror update failed", which contains something like:
>
> To
>
> ! [rem
This GitLab CE issue seems relevant: [1]
(I'm writing this just as I receive another "Remote mirror update failed"
e-mail, this time about the wip/lint-check-version-number branch.)
Ryan S.
-
[1] https://gitlab.com/gitlab-org/gitlab-ce/issues/56222
On Sun, Apr 7, 2019 at 3:30 PM Ben Gamari
Ryan Scott writes:
> To be clear, the wip/dmd-arity is not the only branch I've received e-mails
> about. I've also received "Remove mirror update failed" e-mails of a
> similar caliber that warn about the wip/slowtest, ghc-8.6, ghc-8.8-merges,
> wip/marge_bot_batch_merge_job, and master
To be clear, the wip/dmd-arity is not the only branch I've received e-mails
about. I've also received "Remove mirror update failed" e-mails of a
similar caliber that warn about the wip/slowtest, ghc-8.6, ghc-8.8-merges,
wip/marge_bot_batch_merge_job, and master branches.
Are you not received
Ryan Scott writes:
> Almost every day now I receive an e-mail from GitLab titled "Remote
> mirror update failed", which contains something like:
>
> To
>
> ! [remote rejected] wip/dmd-arity -> wip/dmd-arity (cannot
> lock ref 'refs/heads/wip/dmd-arity': is at
>
Almost every day now I receive an e-mail from GitLab titled "Remote
mirror update failed", which contains something like:
To
! [remote rejected] wip/dmd-arity -> wip/dmd-arity (cannot
lock ref 'refs/heads/wip/dmd-arity': is at
e1cc1254b81a7adadd8db77c7be625497264ab2b but expected
