From: "Sean" <spbrogan@outlook.com>
To: devel@edk2.groups.io, kuqin12@gmail.com
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] UnitTestFrameworkPkg: CI YAML: Grant cmockery spell check exception
Date: Fri, 7 Jan 2022 19:20:51 -0800 [thread overview]
Message-ID: <BY3PR19MB490060528EF88B34BAE8C5EDC84E9@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20220108025448.876-2-kuqin12@gmail.com>
Reviewed-by: Sean Brogan <sean.brogan@microsoft.com>
On 1/7/2022 6:54 PM, Kun Qin wrote:
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3798
>
> UnitTestFrameworkPkg.dec contains cmockery folder from cmocka submodule.
> However, the term "cmockery" is unrecognized by cspell tool.
>
> This change grants spell check exception to "cmockery" to prevent
> pipeline building failure.
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
>
> Signed-off-by: Kun Qin <kuqin12@gmail.com>
> ---
> UnitTestFrameworkPkg/UnitTestFrameworkPkg.ci.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/UnitTestFrameworkPkg/UnitTestFrameworkPkg.ci.yaml b/UnitTestFrameworkPkg/UnitTestFrameworkPkg.ci.yaml
> index 1b247a831593..77d51e13484c 100644
> --- a/UnitTestFrameworkPkg/UnitTestFrameworkPkg.ci.yaml
> +++ b/UnitTestFrameworkPkg/UnitTestFrameworkPkg.ci.yaml
> @@ -89,6 +89,7 @@
> "pytool",
> "pytools",
> "NOFAILURE",
> + "cmockery",
> "DHAVE", # build flag for cmocka in the INF
> "corthon", # Contact GitHub account in Readme
> "mdkinney", # Contact GitHub account in Readme
prev parent reply other threads:[~2022-01-08 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 2:54 [PATCH v1 0/1] Fix pipeline failure from UnitTestFrameworkPkg Kun Qin
2022-01-08 2:54 ` [PATCH v1 1/1] UnitTestFrameworkPkg: CI YAML: Grant cmockery spell check exception Kun Qin
2022-01-08 3:20 ` Sean [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=BY3PR19MB490060528EF88B34BAE8C5EDC84E9@BY3PR19MB4900.namprd19.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