From: Wei Liu <wei.liu2@citrix.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
<anthony.perard@citrix.com>, <xen-devel@lists.xenproject.org>,
<ian.jackson@citrix.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jordan Justen <jordan.l.justen@intel.com>,
<edk2-devel@lists.01.org>, Andrew Fish <afish@apple.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Michael D Kinney <michael.d.kinney@intel.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] Maintainers.txt: update OvmfPkg maintainership
Date: Wed, 23 Aug 2017 10:17:18 +0100 [thread overview]
Message-ID: <20170823091718.uenjj5k4mnnr34q6@citrix.com> (raw)
In-Reply-To: <2a9604db-d19c-97de-3946-9b02092b93a3@redhat.com>
On Wed, Aug 23, 2017 at 11:04:06AM +0200, Laszlo Ersek wrote:
> On 08/23/17 03:30, Konrad Rzeszutek Wilk wrote:
> > It should be fairly simple to expand the 0-day OSSTest to build
> > TianoCore and launch guests with it as a nice regression test.
>
> The point is to catch regressions before they are merged. This requires
> someone who uses Xen every day to review and/or test patches posted to
> edk2-devel that affect Xen code in OVMF.
>
> (If the OSSTest tool can identify and pick such patches from edk2-devel
> automatically, that would work too, of course.)
>
We have been testing OVMF in osstest since two or three years ago,
albeit the test cases are limited to booting and installing a guest.
The regression is going to be caught after patches are merged though
because we're pulling from the official OVMF tree.
prev parent reply other threads:[~2017-08-23 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 17:17 [PATCH] Maintainers.txt: update OvmfPkg maintainership Leif Lindholm
2017-08-16 17:23 ` Kinney, Michael D
2017-08-16 18:02 ` Laszlo Ersek
2017-08-16 19:17 ` Ard Biesheuvel
2017-08-16 18:09 ` Jordan Justen
2017-08-16 18:26 ` Laszlo Ersek
2017-08-16 19:23 ` Leif Lindholm
2017-08-16 22:37 ` Jordan Justen
2017-08-16 23:47 ` Laszlo Ersek
2017-08-17 10:12 ` Leif Lindholm
2017-08-17 11:57 ` Laszlo Ersek
2017-08-23 1:30 ` Konrad Rzeszutek Wilk
2017-08-23 9:04 ` Laszlo Ersek
2017-08-23 9:17 ` Wei Liu [this message]
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=20170823091718.uenjj5k4mnnr34q6@citrix.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