From: "Gao, Liming" <liming.gao@intel.com>
To: "Carsey, Jaben" <jaben.carsey@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH v1 1/1] PatchCheck - add error message for invalid parameter
Date: Fri, 3 Aug 2018 09:44:02 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E2C5578@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <35db4208c876291862f2d0a62d7064793ce08331.1533252046.git.jaben.carsey@intel.com>
Jaben:
Could you give me one failure case? Then, I can further understand the patch.
Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Jaben Carsey
>Sent: Friday, August 03, 2018 7:21 AM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming <liming.gao@intel.com>
>Subject: [edk2] [PATCH v1 1/1] PatchCheck - add error message for invalid
>parameter
>
>Currently if an invalid parameter is passed, it gives a stack trace.
>This changes it to an error message.
>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Yonghong Zhu <yonghong.zhu@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Jaben Carsey <jaben.carsey@intel.com>
>---
> BaseTools/Scripts/PatchCheck.py | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
>diff --git a/BaseTools/Scripts/PatchCheck.py
>b/BaseTools/Scripts/PatchCheck.py
>index 7b7fba8b7044..96b3cdf1fd8a 100755
>--- a/BaseTools/Scripts/PatchCheck.py
>+++ b/BaseTools/Scripts/PatchCheck.py
>@@ -1,7 +1,7 @@
> ## @file
> # Check a patch for various format issues
> #
>-# Copyright (c) 2015 - 2017, Intel Corporation. All rights reserved.<BR>
>+# Copyright (c) 2015 - 2018, Intel Corporation. All rights reserved.<BR>
> #
> # This program and the accompanying materials are licensed and made
> # available under the terms and conditions of the BSD License which
>@@ -528,6 +528,8 @@ class CheckGitCommits:
> print('Checking git commit:', commit)
> patch = self.read_patch_from_git(commit)
> self.ok &= CheckOnePatch(commit, patch).ok
>+ if not commits:
>+ print("Couldn't find commit matching: '{}'".format(rev_spec))
>
> def read_commit_list_from_git(self, rev_spec, max_count):
> # Run git to get the commit patch
>@@ -536,7 +538,7 @@ class CheckGitCommits:
> cmd.append('--max-count=' + str(max_count))
> cmd.append(rev_spec)
> out = self.run_git(*cmd)
>- return out.split()
>+ return out.split() if out else []
>
> def read_patch_from_git(self, commit):
> # Run git to get the commit patch
>@@ -548,7 +550,8 @@ class CheckGitCommits:
> p = subprocess.Popen(cmd,
> stdout=subprocess.PIPE,
> stderr=subprocess.STDOUT)
>- return p.communicate()[0].decode('utf-8', 'ignore')
>+ Result = p.communicate()
>+ return Result[0].decode('utf-8', 'ignore') if Result[0] and
>Result[0].find("fatal")!=0 else None
>
> class CheckOnePatchFile:
> """Performs a patch check for a single file.
>--
>2.16.2.windows.1
>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-08-03 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1533252046.git.jaben.carsey@intel.com>
2018-08-02 23:21 ` [PATCH v1 1/1] PatchCheck - add error message for invalid parameter Jaben Carsey
2018-08-03 9:44 ` Gao, Liming [this message]
2018-08-03 15:06 ` Carsey, Jaben
2018-08-08 1:28 ` Gao, Liming
2018-08-08 3:39 ` Zhu, Yonghong
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E2C5578@SHSMSX104.ccr.corp.intel.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