From: "Guo, Gua" <gua.guo@intel.com>
To: "devel@edk2.groups.io" <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
Date: Thu, 22 Sep 2022 07:12:58 +0000 [thread overview]
Message-ID: <BL1PR11MB547879E8533680947085727AEF4E9@BL1PR11MB5478.namprd11.prod.outlook.com> (raw)
In-Reply-To: <17171D11E1CE1FDF.32370@groups.io>
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 parent reply other threads:[~2022-09-22 7:13 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 ` Guo, Gua [this message]
2022-09-22 16:14 ` [edk2-devel] [PATCH v3 0/2] UnitTestFrameworkPkg: Add code coverage support for GCC Michael D Kinney
2022-09-22 17:17 ` Guo, Gua
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=BL1PR11MB547879E8533680947085727AEF4E9@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