test suite reviews and discussions
 help / color / mirror / Atom feed
From: yaobing <bingx.y.yao@intel.com>
To: dts@dpdk.org
Cc: yaobing <bingx.y.yao@intel.com>
Subject: [dts] [PATCH V1 01/12] tests/unit_tests_cmdline:change hard coding for core numbers
Date: Wed, 24 Oct 2018 10:24:43 +0800	[thread overview]
Message-ID: <1540347894-9652-1-git-send-email-bingx.y.yao@intel.com> (raw)

Cores number is different on different platform,virtual machine maybe
has not assigned cores more than 5 cores,change hard coding for core
numbers in test app startup options

Signed-off-by: yaobing <bingx.y.yao@intel.com>
---
 tests/TestSuite_unit_tests_cmdline.py | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/tests/TestSuite_unit_tests_cmdline.py b/tests/TestSuite_unit_tests_cmdline.py
index 57111e4..1ea228c 100644
--- a/tests/TestSuite_unit_tests_cmdline.py
+++ b/tests/TestSuite_unit_tests_cmdline.py
@@ -37,6 +37,7 @@ Cmdline autotest
 """
 
 from test_case import TestCase
+import utils
 
 #
 #
@@ -57,7 +58,9 @@ class TestUnitTestsCmdline(TestCase):
         Run at the start of each test suite.
         """
         # icc compilation cost long long time.
-        pass
+        cores = self.dut.get_core_list("all")
+        self.coremask = utils.create_mask(cores)
+
     def set_up(self):
         """
         Run before each test case.
@@ -69,7 +72,7 @@ class TestUnitTestsCmdline(TestCase):
         Run cmdline autotests in RTE comand line.
         """
 
-        self.dut.send_expect("./%s/app/test -n 1 -c f" % self.target, "R.*T.*E.*>.*>", 60)
+        self.dut.send_expect("./%s/app/test -n 1 -c %s" % (self.target, self.coremask), "R.*T.*E.*>.*>", 60)
         out = self.dut.send_expect("cmdline_autotest", "RTE>>", 60)
         self.dut.send_expect("quit", "# ")
         self.verify("Test OK" in out, "Test failed")
-- 
2.17.2

             reply	other threads:[~2018-10-24  2:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  2:24 yaobing [this message]
2018-10-24  2:24 ` [dts] [PATCH V1 02/12] tests/unit_tests_crc:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 03/12] tests/unit_tests_dump:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 04/12] tests/unit_tests_kni:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 05/12] tests/unit_tests_lpm:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 06/12] tests/unit_tests_mbuf:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 07/12] tests/unit_tests_mempool:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 08/12] tests/unit_tests_power:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 09/12] tests/unit_tests_qos:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 10/12] tests/unit_tests_ring:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 11/12] tests/unit_tests_ringpmd:change " yaobing
2018-10-24  2:24 ` [dts] [PATCH V1 12/12] tests/unit_tests_timer:change " yaobing
2018-10-24  8:19 ` [dts] [PATCH V1 01/12] tests/unit_tests_cmdline:change " 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=1540347894-9652-1-git-send-email-bingx.y.yao@intel.com \
    --to=bingx.y.yao@intel.com \
    --cc=dts@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).