From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/test: enhance sanity script
Date: Thu, 3 May 2018 11:54:22 +0100 [thread overview]
Message-ID: <0a200d9f-24ac-a0b1-9488-30fb045f7b29@intel.com> (raw)
In-Reply-To: <7AE31235A30B41498D1C31348DC858BD5B3CE252@IRSMSX103.ger.corp.intel.com>
On 03-May-18 11:03 AM, Parthasarathy, JananeeX M wrote:
> Hi Anatoly,
>
> As per the comment " Since file prefixes are not supported, tests cannot be run in parallel"
> Does this means we need not run parallel test group test cases for FreeBSD. So the total test count for FreeBSD will be based on Non-Parallel test groups only.
No, the tests in the "parallel group" can be run in parallel, but on
FreeBSD you cannot run them *in parallel* - that doesn't mean you don't
have to run them :) Just ensure that the thread pool size is set to 1 on
FreeBSD.
>
> Please confirm / share your views on the same.
>
> Thanks
> M.P.Jananee
>
> -----Original Message-----
> From: Burakov, Anatoly
> Sent: Friday, April 27, 2018 7:26 PM
> To: Pattan, Reshma <reshma.pattan@intel.com>; Mcnamara, John <john.mcnamara@intel.com>; dev@dpdk.org
> Cc: Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] app/test: enhance sanity script
>
> On 27-Apr-18 2:20 PM, Reshma Pattan wrote:
>> 1. Sanity Script is enhanced with additional test cases being added to
>> autotest_data.py 2. Fixed in autotest_test_funcs.py to handle test
>> cases which returns "Skipped" as result.
>> The issue was skipped test cases got timed out, causing delay in
>> sanity script execution.
>> 3. Enhanced support for FreeBSD to add the respective memory limit, as
>> FreeBSD doesn't support socket-mem, file-prefix options.
>>
>> Signed-off-by: Jananee Parthasarathy
>> <jananeex.m.parthasarathy@intel.com>
>> ---
>
> <...>
>
>> @@ -1,5 +1,5 @@
>> # SPDX-License-Identifier: BSD-3-Clause -# Copyright(c) 2010-2014
>> Intel Corporation
>> +# Copyright(c) 2010-2018 Intel Corporation
>>
>> # The main logic behind running autotests in parallel
>>
>> @@ -201,6 +201,13 @@ def __init__(self, cmdline, target, blacklist, whitelist):
>> # set up cmdline string
>> def __get_cmdline(self, test):
>> cmdline = self.cmdline
>> + os_name = platform.system()
>> +
>> + # append the respective memory limitation on FREEBSD
>> + # as socket-mem, file-prefix is not supported
>> + if os_name == "FreeBSD" :
>> + cmdline += " -m " + str(sum(map(int, test["Memory"].split(","))))
>> + return cmdline
>
> A better fix would've been to completely avoid calling __get_cmdline() for FreeBSD. Since file prefixes are not supported, tests cannot be run in parallel, so there is no need to limit allocated memory in the first place, so neither -m nor --socket-mem switches need to be added either.
> And without those, there's no need to modify the test cmdline at all.
Also, regarding this - i think what i suggested earlier is slightly
incorrect. A better fix would be to simply return cmdline without
modifications on FreeBSD. Just because we don't modify cmdline now
doesn't mean we wouldn't be doing so in the future, so not calling
__get_cmdline is not the best solution.
>
> --
> Thanks,
> Anatoly
>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-05-03 10:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 13:20 Reshma Pattan
2018-04-27 13:41 ` Burakov, Anatoly
2018-04-27 13:56 ` Burakov, Anatoly
2018-05-03 10:03 ` Parthasarathy, JananeeX M
2018-05-03 10:54 ` Burakov, Anatoly [this message]
2018-05-10 10:36 ` [dpdk-dev] [PATCH v2] " Jananee Parthasarathy
2018-05-13 22:12 ` Thomas Monjalon
2018-05-14 15:26 ` Pattan, Reshma
2018-05-14 15:29 ` Thomas Monjalon
2018-05-15 16:14 ` Parthasarathy, JananeeX M
2018-05-15 16:17 ` Thomas Monjalon
2018-05-18 13:32 ` Parthasarathy, JananeeX M
2018-05-18 13:48 ` Thomas Monjalon
2018-05-20 17:41 ` Parthasarathy, JananeeX M
2018-05-20 19:21 ` Thomas Monjalon
2018-05-15 15:58 ` [dpdk-dev] [PATCH v3 0/3] enhance sanity scripts Jananee Parthasarathy
2018-05-15 15:58 ` [dpdk-dev] [PATCH v3 1/3] app/test: add new test cases to sanity script Jananee Parthasarathy
2018-05-15 16:12 ` Burakov, Anatoly
2018-05-15 15:58 ` [dpdk-dev] [PATCH v3 2/3] app/test: update result for skipped test cases Jananee Parthasarathy
2018-05-15 15:58 ` [dpdk-dev] [PATCH v3 3/3] app/test: enhance freebsd support in sanity script Jananee Parthasarathy
2018-05-23 11:41 ` [dpdk-dev] [PATCH v4 0/4] enhance autotest config and test targets Jananee Parthasarathy
2018-05-23 11:41 ` [dpdk-dev] [PATCH v4 1/4] app/test: enhance autotest config Jananee Parthasarathy
2018-05-23 11:41 ` [dpdk-dev] [PATCH v4 2/4] app/test: update result for skipped test cases Jananee Parthasarathy
2018-05-23 11:41 ` [dpdk-dev] [PATCH v4 3/4] app/test: enhance freebsd support in autotest config Jananee Parthasarathy
2018-05-23 11:41 ` [dpdk-dev] [PATCH v4 4/4] mk: update make targets for classified testcases Jananee Parthasarathy
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=0a200d9f-24ac-a0b1-9488-30fb045f7b29@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=john.mcnamara@intel.com \
--cc=reshma.pattan@intel.com \
/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).