test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yu Jiang <yux.jiang@intel.com>
To: lijuan.tu@intel.com, dts@dpdk.org
Cc: Yu Jiang <yux.jiang@intel.com>
Subject: [dts][PATCH V1 3/4] tests/external_mempool_handler: support eal_param -a to avoid running containers conflict
Date: Wed, 24 May 2023 11:33:27 +0800	[thread overview]
Message-ID: <20230524033328.2146223-4-yux.jiang@intel.com> (raw)
In-Reply-To: <20230524033328.2146223-1-yux.jiang@intel.com>

Support eal_param -a to avoid running containers conflict

Signed-off-by: Yu Jiang <yux.jiang@intel.com>
---
 tests/TestSuite_external_mempool_handler.py | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/tests/TestSuite_external_mempool_handler.py b/tests/TestSuite_external_mempool_handler.py
index 58971e31..c214aae6 100644
--- a/tests/TestSuite_external_mempool_handler.py
+++ b/tests/TestSuite_external_mempool_handler.py
@@ -12,7 +12,7 @@ from framework.pmd_output import PmdOutput
 from framework.test_case import TestCase
 
 
-class TestExternalMempool(TestCase):
+class TestExternalMempoolHandler(TestCase):
     def set_up_all(self):
         """
         Run at the start of each test suite.
@@ -20,7 +20,9 @@ class TestExternalMempool(TestCase):
         self.dut_ports = self.dut.get_ports()
 
         self.verify(len(self.dut_ports) >= 2, "Not enough ports")
-
+        self.eal_param_a = ""
+        for i in self.dut_ports:
+            self.eal_param_a += " -a {}".format(self.dut.ports_info[i]["pci"])
         self.pmdout = PmdOutput(self.dut)
 
         self.app_test_path = self.dut.apps_name["test"]
@@ -33,7 +35,8 @@ class TestExternalMempool(TestCase):
 
     def verify_unit_func(self, ops=""):
         self.dut.send_expect(
-            "./%s -n 4 -c f --mbuf-pool-ops-name %s" % (self.app_test_path, ops),
+            "./%s%s -n 4 -c f --mbuf-pool-ops-name %s"
+            % (self.app_test_path, self.eal_param_a, ops),
             "R.*T.*E.*>.*>",
             60,
         )
@@ -42,7 +45,11 @@ class TestExternalMempool(TestCase):
         self.verify("Test OK" in out, "Mempool autotest failed")
 
     def verify_unit_perf(self):
-        self.dut.send_expect("./%s -n 4 -c f" % self.app_test_path, "R.*T.*E.*>.*>", 60)
+        self.dut.send_expect(
+            "./%s%s -n 4 -c f" % (self.app_test_path, self.eal_param_a),
+            "R.*T.*E.*>.*>",
+            60,
+        )
         out = self.dut.send_expect("mempool_perf_autotest", "RTE>>", 1200)
         self.dut.send_expect("quit", "# ")
         # may need to compare performance
-- 
2.25.1


  parent reply	other threads:[~2023-05-24  3:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  3:33 [dts][PATCH V1 0/4] Support eal_param -a to avoid running containers Yu Jiang
2023-05-24  3:33 ` [dts][PATCH V1 1/4] tests/coremask: support eal_param -a to avoid running containers conflict Yu Jiang
2023-05-24  3:33 ` [dts][PATCH V1 2/4] tests/ethtool_stats: " Yu Jiang
2023-05-24  3:33 ` Yu Jiang [this message]
2023-05-24  3:33 ` [dts][PATCH V1 4/4] tests/multiple_pthread: " Yu Jiang
2023-05-25  2:36   ` lijuan.tu

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=20230524033328.2146223-4-yux.jiang@intel.com \
    --to=yux.jiang@intel.com \
    --cc=dts@dpdk.org \
    --cc=lijuan.tu@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).