Re: EDK II CI failing - Do not submit PRs with "push" label set

Michael D Kinney

Hi Laszlo,

I used the following comments to ask Mergify to re-evaluate the status. The PR has been merged.

@Mergifyio refresh


-----Original Message-----
From: Laszlo Ersek <>
Sent: Monday, December 14, 2020 6:54 AM
To:;; Kinney, Michael D <>
Subject: Re: [edk2-devel] EDK II CI failing - Do not submit PRs with "push" label set

On 12/11/20 22:12, Bret Barkelew via wrote:
Should we just create a Tianocore mirror, rather than relying on someone
(1) TianoCore mirror is a good idea; some other projects too mirror the
submodules they depend on. (Example, IIUC: <>.)

(2) This announcement from Mike, and the associated discussion, are
dated Dec 11th (last Friday, as of this writing), and I can also see
Mike's other (later) announcement "EDK II CI Working - Resume normal
activities". But perhaps I'm still hitting something similar -- in my
current PR <>, there are no
CI failures, but the Mergify bot isn't taking action, despite the "push"
label. I've tried it twice (initial submission, then close+reopen).



- Bret


*From: *Michael D Kinney via
*Sent: *Friday, December 11, 2020 12:16 AM
*To: * <>; Bret Barkelew
<>; Kinney, Michael D
*Subject: *[EXTERNAL] Re: [edk2-devel] EDK II CI failing - Do not submit
PRs with "push" label set


The issue is resolved.

PRs are being processed correctly now.


-----Original Message-----
From: Kinney, Michael D <>
Sent: Thursday, December 10, 2020 10:23 PM
To:; Kinney, Michael D
Subject: EDK II CI failing - Do not submit PRs with "push" label set


The repo for the cmocka submodule is not available right now, and this
is failing
CI checks that run unit tests.  Pre-commit checks that do not have any
unit tests
will pass, but the post commit checks that run everything will always

     PROGRESS - ## Checking Git repository:
     ERROR - Failed to fetch UnitTestFrameworkPkg/Library/CmockaLib/cmocka
     ERROR - Failed to fetch required repository!
     ERROR - Unable to checkout repo due to error

This repo access error to the cmocka has occurred one other time in
the past.  Bret had
suggested the idea of using a different repo for cmocka, perhaps a
fork in GitHub,
to avoid this issue.

We are hoping the issue will be resolved very soon. but until then,
please do not
submit any PRs with a “push” label set.

Best regards,



Join to automatically receive all group messages.