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 these as well? They almost seem to happen any time any
commit is landed.
Ryan S.
On Sat, Apr 6, 2019 at 2:28 PM Ben Gamari wrote:
> 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
> > e1cc1254b81a7adadd8db77c7be625497264ab2b but expected
> > f07b61d047967129a3ae0c56f8894d41c5a9b036)
> >
> > error: failed to push some refs to '[FILTERED]@github.com/ghc/ghc'
> >
> Hmm, how annoying. Strangely, the `wip/dmd-arity` branch currently
> appears to be sitting at the same commit on GitLab and GitHub so I'm not
> really sure what to do here.
>
> sgraf, did you ever push a branch manually to the github.com/ghc/ghc
> mirror?
>
> Cheers,
>
> - Ben
>
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
