From: "Guo, Gua" <gua.guo@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] [PATCH v3 0/2] UnitTestFrameworkPkg: Add code coverage support for GCC
Date: Thu, 22 Sep 2022 17:17:26 +0000 [thread overview]
Message-ID: <BL1PR11MB54788FF00A99A12380941A93EF4E9@BL1PR11MB5478.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO1PR11MB49292E1BDA5B8D7875B75DFCD24E9@CO1PR11MB4929.namprd11.prod.outlook.com>
Is it installed by default in Azure Pipelines Windows agents?
Ans: I think no.
For local developer use cases in Windows, don’t we need to make sure stuart tools install OpenCppCoverage as an external dependency?
Ans: I don't find a good way to auto download and auto install OpenCppCoverage, so choose below way to support it.
So currently use CODE_COVERAGE=TRUE to optional enable it, if want to enable it have below requirement.
For VS2019
Step1. Download and install https://github.com/OpenCppCoverage/OpenCppCoverage/tags
Step2. pip install pycobertura
Step3. stuart_ci_build -c .pytool/CISettings.py -a X64 TOOL_CHAIN_TAG=VS2019 -p MdePkg CODE_COVERAGE=TRUE CC_HTML=TRUE
For GCC5
Step1. sudo apt-get install -y lcov
Step2. pip install lcov_cobertura
Step3. pip install pycobertura
Step4. stuart_ci_build -c .pytool/CISettings.py -a X64 TOOL_CHAIN_TAG=GCC5 -p MdePkg CODE_COVERAGE=TRUE CC_HTML=TRUE
Thanks,
Gua
-----Original Message-----
From: Kinney, Michael D <michael.d.kinney@intel.com>
Sent: Friday, September 23, 2022 12:15 AM
To: Guo, Gua <gua.guo@intel.com>; devel@edk2.groups.io
Cc: Sean Brogan <sean.brogan@microsoft.com>
Subject: RE: [edk2-devel] [PATCH v3 0/2] UnitTestFrameworkPkg: Add code coverage support for GCC
This change adds a dependency on OpenCppCoverage.
However, I do not see any updates to make sure OpenCppCovergae is installed.
Is it installed by default in Azure Pipelines Windows agents?
For local developer use cases in Windows, don’t we need to make sure stuart tools install OpenCppCoverage as an external dependency?
Thanks,
Mike
> -----Original Message-----
> From: Guo, Gua <gua.guo@intel.com>
> Sent: Thursday, September 22, 2022 12:13 AM
> To: devel@edk2.groups.io; Guo, Gua <gua.guo@intel.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Sean Brogan
> <sean.brogan@microsoft.com>
> Subject: RE: [edk2-devel] [PATCH v3 0/2] UnitTestFrameworkPkg: Add
> code coverage support for GCC
>
> It's PR based on the patch. Have any concern, please also share for me.
> https://github.com/tianocore/edk2/pull/3349
>
> Thanks,
> Gua
>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Guo,
> Gua
> Sent: Thursday, September 22, 2022 3:09 PM
> To: devel@edk2.groups.io
> Cc: Guo, Gua <gua.guo@intel.com>
> Subject: [edk2-devel] [PATCH v3 0/2] UnitTestFrameworkPkg: Add code
> coverage support for GCC
>
> From: Gua Guo <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
>
> Gua Guo (2):
> UnitTestFrameworkPkg: Add code coverage support for GCC
> BaseTools/Plugin: Add coverage support for Unit Test
>
> .../HostBasedUnitTestRunner.py | 124 ++++++++++++++++++
> UnitTestFrameworkPkg/ReadMe.md | 42 +++++-
> .../UnitTestFrameworkPkg.ci.yaml | 2 +
> .../UnitTestFrameworkPkgHost.dsc.inc | 3 +-
> 4 files changed, 167 insertions(+), 4 deletions(-)
>
> --
> 2.31.1.windows.1
>
>
>
>
>
next prev parent reply other threads:[~2022-09-22 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17171D11E1CE1FDF.32370@groups.io>
2022-09-22 7:12 ` [edk2-devel] [PATCH v3 0/2] UnitTestFrameworkPkg: Add code coverage support for GCC Guo, Gua
2022-09-22 16:14 ` Michael D Kinney
2022-09-22 17:17 ` Guo, Gua [this message]
2022-09-22 18:20 ` Michael D Kinney
2022-09-22 18:24 ` Michael D Kinney
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=BL1PR11MB54788FF00A99A12380941A93EF4E9@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