From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V1] fix unit_tests_dump key word error
Date: Fri, 10 Nov 2017 10:11:14 +0800 [thread overview]
Message-ID: <1510279874-41429-1-git-send-email-gangx.xu@intel.com> (raw)
the log for dpdk change, so the key word for dts match need change
Signed-off-by: xu,gang <gangx.xu@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 90588cb..e36fa64 100644
--- a/tests/TestSuite_unit_tests_dump.py
+++ b/tests/TestSuite_unit_tests_dump.py
@@ -116,7 +116,7 @@ class TestUnitTestsDump(TestCase):
self.dut.send_expect("./%s/app/test -n 1 -c f" % (self.target), "R.*T.*E.*>.*>", self.start_test_time)
out = self.dut.send_expect("dump_physmem", "RTE>>", self.run_cmd_time * 2)
self.dut.send_expect("quit", "# ")
- elements = ['Segment', 'phys', 'len', 'virt', 'socket_id', 'hugepage_sz', 'nchannel', 'nrank']
+ elements = ['Segment', 'IOVA', 'len', 'virt', 'socket_id', 'hugepage_sz', 'nchannel', 'nrank']
match_regex = "Segment (\d)+:"
for element in elements[1:-1]:
match_regex += " %s:(.*?)," % element
@@ -137,7 +137,7 @@ class TestUnitTestsDump(TestCase):
out = self.dut.send_expect("dump_memzone", "testpmd>", self.run_cmd_time * 2)
self.dut.send_expect("quit", "# ")
- elements = ['Zone', 'name', 'phys', 'len', 'virt', 'socket_id', 'flags']
+ elements = ['Zone', 'name', 'IO', 'len', 'virt', 'socket_id', 'flags']
match_regex = "Zone (\d):"
for element in elements[1:-1]:
match_regex += " %s:(.*?)," % element
--
1.9.3
next reply other threads:[~2017-11-10 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 2:11 xu,gang [this message]
2017-11-10 6:22 ` Liu, Yong
2017-11-20 13:13 ` Liu, Yong
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=1510279874-41429-1-git-send-email-gangx.xu@intel.com \
--to=gangx.xu@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).