test suite reviews and discussions
 help / color / mirror / Atom feed
From: lingwei <weix.ling@intel.com>
To: dts@dpdk.org
Cc: lingwei <weix.ling@intel.com>
Subject: [dts] [PATCH V1] tests/TestSuite_vmdq:delete invalid code in set_up_all and tear_down_all
Date: Mon, 26 Oct 2020 21:39:42 +0800	[thread overview]
Message-ID: <20201026133942.51153-1-weix.ling@intel.com> (raw)

delete invalid code in set_up_all and tear_down_all becasue of
CONFIG_RTE_MAX_QUEUES_PER_PORT default is 1024 in new DPDK.

Signed-off-by: lingwei <weix.ling@intel.com>
---
 tests/TestSuite_vmdq.py | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/tests/TestSuite_vmdq.py b/tests/TestSuite_vmdq.py
index dc4f5ae..3f2ccde 100644
--- a/tests/TestSuite_vmdq.py
+++ b/tests/TestSuite_vmdq.py
@@ -56,8 +56,6 @@ class TestVmdq(TestCase):
         self.verify(len(self.dut_ports) >= 2, "Insufficient ports")
         self.ports_socket = self.dut.get_numa_id(self.dut_ports[0])
 
-        self.dut.send_expect("sed -i 's/CONFIG_RTE_MAX_QUEUES_PER_PORT=256/CONFIG_RTE_MAX_QUEUES_PER_PORT=1024/' ./config/common_base", "# ", 5)
-        self.dut.set_build_options({'RTE_MAX_QUEUES_PER_PORT': 1024})
         self.dut.build_install_dpdk(self.target)
         # Update the max queue per port for Fortville.
         self.dut.send_expect("sed -i 's/define MAX_QUEUES 128/define MAX_QUEUES 1024/' ./examples/vmdq/main.c", "#", 5)
@@ -270,8 +268,4 @@ class TestVmdq(TestCase):
         Run after each test suite.
         """
         # resume setting
-        self.dut.send_expect(
-            "sed -i 's/CONFIG_RTE_MAX_QUEUES_PER_PORT=1024/CONFIG_RTE_MAX_QUEUES_PER_PORT=256/' ./config/common_base",
-            "# ", 5)
-        self.dut.set_build_options({'RTE_MAX_QUEUES_PER_PORT': 256})
         self.dut.build_install_dpdk(self.target)
-- 
2.17.1


             reply	other threads:[~2020-10-26  5:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 13:39 lingwei [this message]
2020-10-26  5:45 ` Ling, WeiX
2020-10-29  8:15 ` Ma, LihongX
2020-11-03  2:15   ` 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=20201026133942.51153-1-weix.ling@intel.com \
    --to=weix.ling@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).