test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Xiao, QimaiX" <qimaix.xiao@intel.com>
To: "Jiang, YuX" <yux.jiang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Jiang, YuX" <yux.jiang@intel.com>
Subject: Re: [dts] [PATCH V1] tests/unit_tests_eal: modify cores for	hash_readwrite_perf_autotest
Date: Wed, 19 Feb 2020 09:28:10 +0000	[thread overview]
Message-ID: <7d5448a3e7bf429ea8077aca251edb01@intel.com> (raw)
In-Reply-To: <1582099661-64030-1-git-send-email-yux.jiang@intel.com>

Tested-by: Xiao Qimai <qimaix.xiao@intel.com>

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Jiang,yu
> Sent: Wednesday, February 19, 2020 4:08 PM
> To: dts@dpdk.org
> Cc: Jiang, YuX <yux.jiang@intel.com>
> Subject: [dts] [PATCH V1] tests/unit_tests_eal: modify cores for
> hash_readwrite_perf_autotest
> 
> 
> hash_readwrite_perf_autotest need at least 3 cores to test
> 
> Signed-off-by: Jiang,yu <yux.jiang@intel.com>
> ---
>  tests/TestSuite_unit_tests_eal.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/TestSuite_unit_tests_eal.py
> b/tests/TestSuite_unit_tests_eal.py
> index bd1696b..9c80663 100644
> --- a/tests/TestSuite_unit_tests_eal.py
> +++ b/tests/TestSuite_unit_tests_eal.py
> @@ -191,7 +191,7 @@ class TestUnitTestsEal(TestCase):
>          Run hash readwrite perf autotest.
>          """
> 
> -        eal_params = self.dut.create_eal_parameters()
> +        eal_params = self.dut.create_eal_parameters(cores='1S/4C/1T')
>          self.dut.send_expect("./%s/app/test %s" % (self.target,eal_params),
>                               "R.*T.*E.*>.*>", self.start_test_time)
>          out = self.dut.send_expect("hash_readwrite_perf_autotest",
> --
> 1.9.3


  reply	other threads:[~2020-02-19  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19  8:07 Jiang,yu
2020-02-19  9:28 ` Xiao, QimaiX [this message]
2020-02-21  1:56 ` Tu, Lijuan

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=7d5448a3e7bf429ea8077aca251edb01@intel.com \
    --to=qimaix.xiao@intel.com \
    --cc=dts@dpdk.org \
    --cc=yux.jiang@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).