From: ChenBo <box.c.chen@intel.com>
To: dts@dpdk.org
Cc: ChenBo <box.c.chen@intel.com>
Subject: [dts] [PATCH V1] tests/unit_tests_dump: Update of adaptive dpdk
Date: Thu, 22 Oct 2020 16:11:49 +0800 [thread overview]
Message-ID: <20201022081149.5568-1-box.c.chen@intel.com> (raw)
DPDK has modified the print log, commit: 26cbb4191e91c07e8f498949b15ad33659797996
DTS needs to be adapted and updated.
Signed-off-by: ChenBo <box.c.chen@intel.com>
---
tests/TestSuite_unit_tests_dump.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/TestSuite_unit_tests_dump.py b/tests/TestSuite_unit_tests_dump.py
index 603cc1a..336cce2 100644
--- a/tests/TestSuite_unit_tests_dump.py
+++ b/tests/TestSuite_unit_tests_dump.py
@@ -102,7 +102,7 @@ class TestUnitTestsDump(TestCase):
# Nic driver will create multiple rings.
# Only check the last one to make sure ring_dump function work.
- self.verify( 'MP_mbuf_pool_socket_0' in results, "dump ring name failed")
+ self.verify( 'MP_mb_pool_0' in results, "dump ring name failed")
for result in results:
self.dut.send_expect("%s" % cmd, "testpmd>", self.start_test_time)
out = self.dut.send_expect("dump_ring %s" % result, "testpmd>", self.run_cmd_time)
@@ -123,7 +123,7 @@ class TestUnitTestsDump(TestCase):
m = re.compile(r"%s" % match_regex, re.S)
results = m.findall(out)
- self.verify(results[0][0] == 'mbuf_pool_socket_0', "dump mempool name failed")
+ self.verify(results[0][0] == 'mb_pool_0', "dump mempool name failed")
for result in results:
self.dut.send_expect("%s" % cmd, "testpmd>", self.start_test_time)
out = self.dut.send_expect("dump_mempool %s" % result[0], "testpmd>", self.run_cmd_time * 2)
--
2.17.1
next reply other threads:[~2020-10-22 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 8:11 ChenBo [this message]
2020-10-22 8:41 ` Chen, BoX C
2020-11-03 1:50 ` 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=20201022081149.5568-1-box.c.chen@intel.com \
--to=box.c.chen@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).