From: "Laszlo Ersek" <lersek@redhat.com>
To: Sean Brogan <spbrogan@outlook.com>,
devel@edk2.groups.io, michael.d.kinney@intel.com,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>,
Rebecca Cran <rebecca@bsdio.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] running CI locally
Date: Fri, 21 Aug 2020 09:23:32 +0200 [thread overview]
Message-ID: <5ca9187c-96f3-53f1-0ac0-809bc1156ece@redhat.com> (raw)
In-Reply-To: <2d9572c6-7549-d0ae-3ec9-95158cfef484@redhat.com>
Hi Mike, Sean;
On 08/19/20 19:59, Laszlo Ersek wrote:
> I'll report back with more results.
I installed a Fedora 32 Server VM.
Installed the "mono-complete" package (+its deps).
Installed the "nodejs" package.
Installed "cspell" (+deps) with "npm" (with the latter coming from the
nodejs package).
Edk2 checked out at current HEAD
(5a6d764e1d073d28e8f398289ccb5592bf9a72ba).
* Platform CI results:
- <https://github.com/tianocore/edk2/tree/master/OvmfPkg/PlatformCI>:
Built successfully for IA32, X64, and IA32X64 (toolchain: GCC5).
- <https://github.com/tianocore/edk2/tree/master/ArmVirtPkg/PlatformCI>:
Built successfully for ARM and AARCH64 (toolchain: GCC5).
* Core CI results:
- <https://github.com/tianocore/edk2/blob/master/.pytool/Readme.md>
Complete run successful (toolchain: GCC5); no package / arch / target
/ test restrictions.
I got the following WARNINGs:
- ArmVirtPkg, EmulatorPkg, and OvmfPkg are covered by Platform CI, not
Core CI -- these are expected:
> PROGRESS - --Running ArmVirtPkg: Compiler Plugin DEBUG --
> WARNING - --->Test Skipped: in plugin! Compiler Plugin DEBUG
> PROGRESS - --Running ArmVirtPkg: Compiler Plugin RELEASE --
> WARNING - --->Test Skipped: in plugin! Compiler Plugin RELEASE
> PROGRESS - --Running EmulatorPkg: Compiler Plugin DEBUG --
> WARNING - --->Test Skipped: in plugin! Compiler Plugin DEBUG
> PROGRESS - --Running EmulatorPkg: Compiler Plugin RELEASE --
> WARNING - --->Test Skipped: in plugin! Compiler Plugin RELEASE
> PROGRESS - --Running OvmfPkg: Compiler Plugin DEBUG --
> WARNING - --->Test Skipped: in plugin! Compiler Plugin DEBUG
> PROGRESS - --Running OvmfPkg: Compiler Plugin RELEASE --
> WARNING - --->Test Skipped: in plugin! Compiler Plugin RELEASE
- ArmVirtPkg, DynamicTablesPkg, CryptoPkg, EmulatorPkg, FatPkg,
NetworkPkg, OvmfPkg, PcAtChipsetPkg, SecurityPkg and ShellPkg are
not covered by host-based unit tests -- I think also expected:
> PROGRESS - --Running ArmVirtPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running DynamicTablesPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running CryptoPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running EmulatorPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running FatPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running NetworkPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running OvmfPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running PcAtChipsetPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running SecurityPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
> PROGRESS - --Running ShellPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Compiler Plugin NOOPT
- I'm not really sure about the following warnings. They were emitted
for a subset of the above packages. I read the docs at
<https://github.com/tianocore/edk2/blob/master/.pytool/Readme.md#host-module-inclusion-test---hostunittestdsccompletecheck>
but I still don't understand :)
> PROGRESS - --Running CryptoPkg: Host Unit Test Dsc Complete Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Dsc Complete Check Test NO-TARGET
> PROGRESS - --Running FatPkg: Host Unit Test Dsc Complete Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Dsc Complete Check Test NO-TARGET
> PROGRESS - --Running NetworkPkg: Host Unit Test Dsc Complete Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Dsc Complete Check Test NO-TARGET
> PROGRESS - --Running PcAtChipsetPkg: Host Unit Test Dsc Complete Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Dsc Complete Check Test NO-TARGET
> PROGRESS - --Running SecurityPkg: Host Unit Test Dsc Complete Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Dsc Complete Check Test NO-TARGET
> PROGRESS - --Running ShellPkg: Host Unit Test Dsc Complete Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Host Unit Test Dsc Complete Check Test NO-TARGET
- Still related to host-based unit tests, I believe the following
warnings, for FmpDevicePkg, MdeModulePkg, MdePkg, UefiCpuPkg, and
UnitTestFrameworkPkg, report that running the tests on the build
host (understandably) prevents the tests from covering all edk2
architectures:
> PROGRESS - --Running FmpDevicePkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - Allowing Override for key TARGET_ARCH
> PROGRESS - --Running MdeModulePkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - Allowing Override for key TARGET_ARCH
> PROGRESS - --Running MdePkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - Allowing Override for key TARGET_ARCH
> PROGRESS - --Running UefiCpuPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - Allowing Override for key TARGET_ARCH
> PROGRESS - --Running UnitTestFrameworkPkg: Host Unit Test Compiler Plugin NOOPT --
> WARNING - Allowing Override for key TARGET_ARCH
- The below seems to be related to the "spell checking in audit
mode" known issues at
<https://github.com/tianocore/edk2/blob/master/.pytool/Readme.md>.
What does "audit mode" mean?
FWIW, the packages listed below (EmulatorPkg, MdeModulePkg,
MdePkg, NetworkPkg, OvmfPkg, ShellPkg, UefiCpuPkg) is a proper
subset of the packges noted in ".pytool/Readme.md" -- the latter
mentions CryptoPkg and SecurityPkg in addition.
> PROGRESS - --Running EmulatorPkg: Spell Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Spell Check Test NO-TARGET
> PROGRESS - --Running MdeModulePkg: Spell Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Spell Check Test NO-TARGET
> PROGRESS - --Running MdePkg: Spell Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Spell Check Test NO-TARGET
> PROGRESS - --Running NetworkPkg: Spell Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Spell Check Test NO-TARGET
> PROGRESS - --Running OvmfPkg: Spell Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Spell Check Test NO-TARGET
> PROGRESS - --Running ShellPkg: Spell Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Spell Check Test NO-TARGET
> PROGRESS - --Running UefiCpuPkg: Spell Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Spell Check Test NO-TARGET
- Not sure about the last one:
> PROGRESS - --Running FatPkg: Library Class Check Test NO-TARGET --
> WARNING - --->Test Skipped: in plugin! Library Class Check Test NO-TARGET
* One suggestion (in addition to the others made in this thread):
- Please add "BaseToolsBuild" to "BaseTools/.gitignore".
* A question:
- On github, there is some logic that restricts the full Core CI build
to packages that may be affected by a patch series. Is this available
locally?
According to the Core CI documentation, the "stuart_ci_build" command
can be limited with "-p" / "-a" / "-t" flags; given a commit range,
how do we calculate the "tightest" flag values?
Thank you very much!
Laszlo
next prev parent reply other threads:[~2020-08-21 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 12:27 running CI locally Laszlo Ersek
2020-08-19 15:29 ` [edk2-devel] " Michael D Kinney
2020-08-19 16:22 ` Sean
2020-08-19 17:59 ` Laszlo Ersek
2020-08-21 7:23 ` Laszlo Ersek [this message]
2020-08-21 21:36 ` Sean
2020-08-24 12:35 ` Laszlo Ersek
[not found] ` <162D662A3371B4DC.7353@groups.io>
2020-08-21 21:50 ` Sean
2020-08-19 17:56 ` 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=5ca9187c-96f3-53f1-0ac0-809bc1156ece@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