From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: EDK II CI failing - Do not submit PRs with "push" label set
Date: Fri, 11 Dec 2020 21:12:46 +0000 [thread overview]
Message-ID: <MWHPR21MB0160EFF6A970971473E3AB0BEFCA1@MWHPR21MB0160.namprd21.prod.outlook.com> (raw)
In-Reply-To: <BL0PR11MB32362891C7B3AD178CA3584ED2CA0@BL0PR11MB3236.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]
Should we just create a Tianocore mirror, rather than relying on someone else?
- Bret
From: Michael D Kinney via groups.io<mailto:michael.d.kinney=intel.com@groups.io>
Sent: Friday, December 11, 2020 12:16 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Bret Barkelew<mailto:Bret.Barkelew@microsoft.com>; Kinney, Michael D<mailto:michael.d.kinney@intel.com>
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.
Mike
> -----Original Message-----
> From: Kinney, Michael D <michael.d.kinney@intel.com>
> Sent: Thursday, December 10, 2020 10:23 PM
> To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>; bret.barkelew@microsoft.com
> Subject: EDK II CI failing - Do not submit PRs with "push" label set
>
> Hello,
>
> 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 fail.
>
> PROGRESS - ## Checking Git repository: UnitTestFrameworkPkg/Library/CmockaLib/cmocka...
> ERROR - Failed to fetch UnitTestFrameworkPkg/Library/CmockaLib/cmocka
> ERROR - FAILED!
> 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,
>
> Mike
>
[-- Attachment #2: Type: text/html, Size: 4018 bytes --]
next prev parent reply other threads:[~2020-12-11 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 6:22 EDK II CI failing - Do not submit PRs with "push" label set Michael D Kinney
2020-12-11 7:30 ` Michael D Kinney
2020-12-11 21:16 ` [edk2-devel] " Rebecca Cran
2020-12-11 21:18 ` [EXTERNAL] " Bret Barkelew
2020-12-11 8:16 ` Michael D Kinney
2020-12-11 21:12 ` Bret Barkelew [this message]
2020-12-14 14:54 ` [edk2-devel] " Laszlo Ersek
2020-12-14 17:30 ` Michael D Kinney
2020-12-14 18:59 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR21MB0160EFF6A970971473E3AB0BEFCA1@MWHPR21MB0160.namprd21.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox