From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] app/test: fix autotest_runner crash
Date: Wed, 12 Jun 2019 15:18:44 +0100 [thread overview]
Message-ID: <c9241d85-a976-94d8-615c-73bba86bd66e@intel.com> (raw)
In-Reply-To: <20190612133323.43530-1-herakliusz.lipiec@intel.com>
On 12-Jun-19 2:33 PM, Herakliusz Lipiec wrote:
> On some systems when dpdk test is executed with make test command
> autotest_runner crashes in first_cpu_on_node. This happens when list
> of available cpus contains something that is not a cpu as first element.
> Fixed by removing all non-cpu values from list of available cpus.
>
> Bugzilla ID: 253
> Fixes: 22dcd9a4d90f ("test: parallelize unit tests")
> Cc: anatoly.burakov@intel.com
> Cc: stable@dpdk.org
> Signed-off-by: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
> ---
> app/test/autotest_runner.py | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/app/test/autotest_runner.py b/app/test/autotest_runner.py
> index b72716e1e..7aece8905 100644
> --- a/app/test/autotest_runner.py
> +++ b/app/test/autotest_runner.py
> @@ -43,11 +43,10 @@ def get_numa_nodes():
> # find first (or any, really) CPU on a particular node, will be used to spread
> # processes around NUMA nodes to avoid exhausting memory on particular node
> def first_cpu_on_node(node_nr):
> - cpu_path = glob.glob("/sys/devices/system/node/node%d/cpu*" % node_nr)[0]
> - cpu_name = os.path.basename(cpu_path)
> - m = re.match(r"cpu(\d+)", cpu_name)
> - return int(m.group(1))
> -
This is an unnecessary whitespace change.
> + cpu_path = glob.glob("/sys/devices/system/node/node%d/cpu*" % node_nr)
> + r = re.compile(r"cpu(\d+)")
> + cpu_name = filter(None ,map(r.match, map(os.path.basename, cpu_path)))
Typo, should be "None, map" rather than "None ,map". Also, perhaps
splitting this on multiple lines would benefit readability, like this:
cpu_name = filter(None,
map(r.match,
map(os.path.basename, cpu_path)
)
)
No preference though, can be left as is.
> + return int(next(iter(cpu_name)).group(1))
IMO too much going on on one line, maybe leave the return as it was and
just fix the match? As in,
m = next(iter(cpu_name))
return int(m.group(1))
Also probably needs a comment explaining why iter() is there - namely,
that return value from a filter is a list in Python 2, but a generator
in Python 3, and next() only works with generators.
Otherwise,
Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
>
> pool_child = None # per-process child
>
>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-06-12 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 13:33 Herakliusz Lipiec
2019-06-12 14:18 ` Burakov, Anatoly [this message]
2019-06-12 14:46 ` [dpdk-stable] [PATCH v2] " Herakliusz Lipiec
2019-06-12 14:48 ` Burakov, Anatoly
2019-07-04 21:19 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=c9241d85-a976-94d8-615c-73bba86bd66e@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=herakliusz.lipiec@intel.com \
--cc=stable@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).