From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next v2 1/5] support/scripts/pkg-stats-new: rewrite in Python
Date: Wed, 7 Mar 2018 23:35:19 +0100 [thread overview]
Message-ID: <20180307233519.6eeda226@windsurf> (raw)
In-Reply-To: <5a8e23dda8705_24263ff17ca48f783320@ultri3.mail>
Hello,
On Wed, 21 Feb 2018 22:58:53 -0300, Ricardo Martincoski wrote:
> This method is missing patches in subdirs for binutils, gdb, ...
>
> for pkg in packages:
> pkg.patch_count = 0
> for subdir, _, _ in os.walk(pkgdir):
> pkg.patch_count += len(fnmatch.filter(os.listdir(subdir), '*.patch'))
ACK, already fixed for v3.
> > +def get_check_package_warnings(pkgdir):
> > + cmd = ["./utils/check-package"]
> > + for root, dirs, files in os.walk(pkgdir):
> > + for f in files:
> > + if f.endswith(".mk") or f.endswith(".hash") or f == "Config.in" or f == "Config.in.host":
> > + cmd.append(f)
>
> Here you need:
> cmd.append(os.path.join(root, f))
> otherwise the whole column is filled with zeros.
Indeed. Fixed for v3.
>
> > + o = subprocess.check_output(cmd, stderr=subprocess.STDOUT)
>
> When above line is fixed, this command can return non-zero code that leads to
> exception CalledProcessError. There are a few ways to solve it:
>
> 1)
> o = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE).communicate()[1]
> 2)
> try:
> ...
> except ...
> 3) change check-package, adding an option to always return code zero.
>
> IMO, option 1 is the better one.
Agreed, fixed for v3 as well.
Thanks for the review!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-03-07 22:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 22:13 [Buildroot] [PATCH next v2 0/5] New pkg-stats script, with version information Thomas Petazzoni
2018-02-21 22:13 ` [Buildroot] [PATCH next v2 1/5] support/scripts/pkg-stats-new: rewrite in Python Thomas Petazzoni
2018-02-22 1:58 ` Ricardo Martincoski
2018-03-07 22:35 ` Thomas Petazzoni [this message]
2018-02-21 22:13 ` [Buildroot] [PATCH next v2 2/5] support/scripts/pkg-stats-new: add -n and -p options Thomas Petazzoni
2018-02-24 4:54 ` Ricardo Martincoski
2018-03-07 22:35 ` Thomas Petazzoni
2018-02-21 22:13 ` [Buildroot] [PATCH next v2 3/5] support/scripts/pkg-stats-new: add current version information Thomas Petazzoni
2018-02-26 0:47 ` Ricardo Martincoski
2018-03-07 22:25 ` Thomas Petazzoni
2018-03-08 3:14 ` Ricardo Martincoski
2018-03-08 7:48 ` Thomas Petazzoni
2018-02-21 22:13 ` [Buildroot] [PATCH next v2 4/5] support/scripts/pkg-stats-new: add latest upstream " Thomas Petazzoni
2018-02-28 3:03 ` Ricardo Martincoski
2018-03-07 22:41 ` Thomas Petazzoni
2018-03-08 9:52 ` Ricardo Martincoski
2018-03-08 9:56 ` Thomas Petazzoni
2018-03-09 2:41 ` Ricardo Martincoski
2018-03-21 20:58 ` Thomas Petazzoni
2018-03-22 3:11 ` Ricardo Martincoski
2018-03-22 7:53 ` Thomas Petazzoni
2018-03-21 21:35 ` Thomas Petazzoni
2018-03-22 3:17 ` Ricardo Martincoski
2018-03-22 10:01 ` Thomas Petazzoni
2018-02-21 22:13 ` [Buildroot] [PATCH next v2 5/5] support/scripts/pkg-stats: replace with new Python version Thomas Petazzoni
2018-02-24 17:55 ` [Buildroot] [PATCH next v2 0/5] New pkg-stats script, with version information Arnout Vandecappelle
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-all 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=20180307233519.6eeda226@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.