From: "Rebecca Cran" <rebecca@bsdio.com>
To: Sean Brogan <spbrogan@outlook.com>,
devel@edk2.groups.io, lersek@redhat.com
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
Jordan L Justen <jordan.l.justen@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] Add BhyvePkg, to support the bhyve hypervisor
Date: Fri, 31 Jul 2020 14:28:38 -0600 [thread overview]
Message-ID: <5ac86be3-8ff9-d428-fc5c-2e72fbf98faf@bsdio.com> (raw)
In-Reply-To: <BN8PR07MB6962FCCA9AB09F8A6DCCED69C84E0@BN8PR07MB6962.namprd07.prod.outlook.com>
On 7/31/20 11:32 AM, Sean Brogan wrote:
> This patch as committed is breaking CI. It was not captured in PR
> because the PR optimizes to detect packages impacted by the commits
> and the BhyvePkg addition is not depended on by other packages (that
> are in CI). BhyvePkg which is nested inside OvmfPkg ( a violation of
> DEC spec: see
> https://edk2-docs.gitbook.io/edk-ii-dec-specification/2_dec_file_overview
> paragraph 4) does not support CI so it is not tested but now that it
> is in the edk2 tree it is causing the other packages to fail.
Sorry. I've replicated the errors locally, and will see if I can work
around them.
--
Rebecca Cran
next prev parent reply other threads:[~2020-07-31 20:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 5:41 [PATCH 0/1] Add BhyvePkg, to support the bhyve hypervisor Rebecca Cran
2020-07-13 5:41 ` [PATCH 1/1] " Rebecca Cran
2020-07-13 16:16 ` [edk2-devel] " Laszlo Ersek
2020-07-13 20:24 ` Rebecca Cran
2020-07-13 16:55 ` Laszlo Ersek
2020-07-13 18:09 ` Laszlo Ersek
2020-07-13 20:25 ` Rebecca Cran
[not found] ` <162169B0F92549B8.20689@groups.io>
2020-07-31 5:17 ` Rebecca Cran
2020-07-31 13:07 ` Laszlo Ersek
2020-07-31 13:10 ` Laszlo Ersek
2020-07-31 17:32 ` Sean
2020-07-31 20:28 ` Rebecca Cran [this message]
2020-07-31 21:14 ` Laszlo Ersek
2020-08-01 15:54 ` Laszlo Ersek
2020-08-01 21:10 ` Laszlo Ersek
2020-07-13 5:43 ` [PATCH 0/1] " Liming Gao
2020-07-13 5:48 ` Rebecca Cran
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=5ac86be3-8ff9-d428-fc5c-2e72fbf98faf@bsdio.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