From: "Laszlo Ersek" <lersek@redhat.com>
To: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>,
"Gao, Zhichao" <zhichao.gao@intel.com>,
devel@edk2.groups.io
Cc: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
Maciej Rabeda <maciej.rabeda@linux.intel.com>,
"Wu, Jiaxin" <jiaxin.wu@intel.com>,
"Fu, Siyuan" <siyuan.fu@intel.com>, "Ni, Ray" <ray.ni@intel.com>,
Nd <nd@arm.com>, gaoliming <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [PATCH v12 1/1] ShellPkg/DynamicCommand: add HttpDynamicCommand
Date: Tue, 22 Sep 2020 08:40:37 +0200 [thread overview]
Message-ID: <3d47afa4-a273-dd4e-3000-484ea691649e@redhat.com> (raw)
In-Reply-To: <20e71bc1c6075ddbd280597ac6f61c82@mail.gmail.com>
On 09/17/20 18:55, Vladimir Olovyannikov wrote:
> Laszlo, what is the outcome? Were you able to run these tests locally?
> Is there any step-by-step instruction I can follow?
- See my comments at:
- https://edk2.groups.io/g/devel/message/64428
- https://edk2.groups.io/g/devel/message/64528
You don't need to go through that entire email; the main points are
that I used a separate VM (namely a Fedora 32 Server guest) and in the
VM, a python3 virtual environment, for running CI locally. Plus that I
had to install some packages manually.
- For building ShellPkg, see the Core CI documentation:
https://github.com/tianocore/edk2/blob/master/.pytool/Readme.md#running-ci-locally
- For building the new dynamic command as part of OVMF, first apply your
patches for TianoCore#2857, and then see the Platform CI
documentation:
https://github.com/tianocore/edk2/tree/master/OvmfPkg/PlatformCI
Thanks
Laszlo
prev parent reply other threads:[~2020-09-22 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 18:04 [PATCH v12 0/1] ShellPkg/DynamicCommand: add HttpDynamicCommand Vladimir Olovyannikov
2020-09-15 18:04 ` [PATCH v12 1/1] " Vladimir Olovyannikov
2020-09-17 2:28 ` [edk2-devel] " Gao, Zhichao
2020-09-17 16:55 ` Vladimir Olovyannikov
2020-09-22 6:40 ` Laszlo Ersek [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=3d47afa4-a273-dd4e-3000-484ea691649e@redhat.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