From: "Guo, Gua" <gua.guo@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Guo, Gua" <gua.guo@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Michael Kubacki <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] [PATCH v8 0/3] Add code coverage support for GCC/MSVC
Date: Mon, 2 Jan 2023 11:56:37 +0000 [thread overview]
Message-ID: <BL1PR11MB5478154BCE7558EA95573CC1EFF79@BL1PR11MB5478.namprd11.prod.outlook.com> (raw)
In-Reply-To: <17367A3BDC508760.4716@groups.io>
[-- Attachment #1.1: Type: text/plain, Size: 2983 bytes --]
@Kinney, Michael D<mailto:michael.d.kinney@intel.com> and @Michael Kubacki<mailto:mikuback@linux.microsoft.com> everything fix now.
Leverage ReportGenerator https://marketplace.visualstudio.com/items?itemName=Palmmedia.reportgenerator to create code coverage pipeline.
PR: https://github.com/tianocore/edk2/pull/3349
"Job2 (Build Agent : windows-2019)" must require for Windows build agent because ReportGenerator is "Windows dot-net" specific. So I add some dependency to let it support for both GCC5 and VS2019.
* Windows-VS2019 flow
* Summary URL: https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=75021&view=results
[cid:image003.png@01D91EE2.B62A06B0]
* CI/CD Flow:
[cid:image001.png@01D91EE0.6BDEEE60]
* Ubuntu-GCC5 flow
* Summary URL: https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=75020&view=results
[cid:image004.png@01D91EE4.4A236270]
* CI/CD Flow:
[cid:image002.png@01D91EE0.D7B262C0]
Thanks,
Gua
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Guo, Gua
Sent: Monday, January 2, 2023 7:25 PM
To: devel@edk2.groups.io
Cc: Guo, Gua <gua.guo@intel.com>
Subject: [edk2-devel] [PATCH v8 0/3] Add code coverage support for GCC/MSVC
From: Gua Guo <gua.guo@intel.com<mailto:gua.guo@intel.com>>
V1: Add coverage option for GCC
V2: Add ReadMe.md for how to generate coverage report
V3: Add VS2019 and GCC code coverage support
V4: Add VS2019 and GCC Azure CI/CD support
V5: Fix some typo and some flow issue
V6: Remove html coverage information
- Due to python 3.11 install lxml will be failure,
pycobertura need it to convert cobertura format to
html file.
- Add section for developer how to use OpenCppCoverage
on IDE Visual Studio
V7: Remove redundant code and add code coverage pipeline support
- Remove redundant code on HostBasedUnitTestRunner.py
- Unify coding rule on HostBasedUnitTestRunner.py
- Add CodeCoverage Azure pipeline support for GCC5 and VS2019
Gua Guo (3):
UnitTestFrameworkPkg: Add code coverage support for GCC
BaseTools/Plugin: Add coverage support for Unit Test
.azurepipelines: Install code coverage tool
.azurepipelines/Ubuntu-GCC5.yml | 5 +-
.azurepipelines/Windows-VS2019.yml | 5 +
.../templates/pr-gate-build-job.yml | 36 +++++++
.azurepipelines/templates/pr-gate-steps.yml | 4 +
.../HostBasedUnitTestRunner.py | 101 +++++++++++++++++-
UnitTestFrameworkPkg/ReadMe.md | 41 +++++++
.../UnitTestFrameworkPkg.ci.yaml | 1 +
.../UnitTestFrameworkPkgHost.dsc.inc | 3 +-
pip-requirements.txt | 2 +
9 files changed, 195 insertions(+), 3 deletions(-)
--
2.31.1.windows.1
[-- Attachment #1.2: Type: text/html, Size: 12590 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 35196 bytes --]
[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 35672 bytes --]
[-- Attachment #4: image003.png --]
[-- Type: image/png, Size: 49263 bytes --]
[-- Attachment #5: image004.png --]
[-- Type: image/png, Size: 54363 bytes --]
next parent reply other threads:[~2023-01-02 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17367A3BDC508760.4716@groups.io>
2023-01-02 11:56 ` Guo, Gua [this message]
2023-01-02 18:01 ` [edk2-devel] [PATCH v8 0/3] Add code coverage support for GCC/MSVC Michael D Kinney
2023-01-03 15:54 ` Michael Kubacki
2023-01-02 11:24 Guo, Gua
2023-01-02 18:05 ` [edk2-devel] " Michael D Kinney
2023-01-03 16:14 ` Michael Kubacki
2023-01-04 2:49 ` Sean
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=BL1PR11MB5478154BCE7558EA95573CC1EFF79@BL1PR11MB5478.namprd11.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