From: "Liu, Yong" <yong.liu@intel.com>
To: "Lu, PeipeiX" <peipeix.lu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Lu, PeipeiX" <peipeix.lu@intel.com>
Subject: Re: [dts] [PATCH V1] Regular expressions don't match
Date: Mon, 14 Aug 2017 08:53:19 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62E530FC@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1502699127-70950-1-git-send-email-peipeix.lu@intel.com>
Peipei,
I think your commit log is not so accurate. The root cause is that "MP_mbuf_pool_socket_0" is no longer the first mempool.
So the check function will be failed. Please modify your commit log.
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lu,peipei
> Sent: Monday, August 14, 2017 4:25 PM
> To: dts@dpdk.org
> Cc: Lu, PeipeiX <peipeix.lu@intel.com>
> Subject: [dts] [PATCH V1] Regular expressions don't match
>
> Output format is:
> ring <HT_fdir_0000:05:00.0>@0x7f03bff6e500
> flags=0
> ring <HT_l2_tn_0000:05:00.0>@0x7f03bfc6dc00
> flags=0
> ring <HT_fdir_0000:05:00.1>@0x7f03bfc22780
> flags=0
> ring <MP_mbuf_pool_socket_0>@0x7f03a724c580
> flags=0
> Original regex format can not parse it for "MP_mbuf_pool_socket_0"
> New regex format is "ring <(.*?)>"
>
>
>
>
> Signed-off-by: lu,peipei <peipeix.lu@intel.com>
> ---
> tests/TestSuite_unit_tests_dump.py | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/TestSuite_unit_tests_dump.py
> b/tests/TestSuite_unit_tests_dump.py
> index 03c9554..90588cb 100644
> --- a/tests/TestSuite_unit_tests_dump.py
> +++ b/tests/TestSuite_unit_tests_dump.py
> @@ -88,13 +88,13 @@ class TestUnitTestsDump(TestCase):
> self.dut.send_expect("./%s/app/testpmd -n 1 -c f -- -i" %
> (self.target), "testpmd>", self.start_test_time)
> out = self.dut.send_expect("dump_ring", "testpmd>",
> self.run_cmd_time)
> self.dut.send_expect("quit", "# ")
> - match_regex = "ring <(.*?)>@0x(.*)\r\n"
> + match_regex = "ring <(.*?)>"
> m = re.compile(r"%s" % match_regex, re.S)
> result = m.findall(out)
>
> # 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 result[0], "dump ring
> name failed")
> + self.verify( 'MP_mbuf_pool_socket_0' in result, "dump ring name
> failed")
>
> def test_mempool_dump(self):
> """
> @@ -107,7 +107,7 @@ class TestUnitTestsDump(TestCase):
> m = re.compile(r"%s" % match_regex, re.S)
> result = m.findall(out)
>
> - self.verify(result[0][0] == 'MP_mbuf_pool_socket_0', "dump
> mempool name failed")
> + self.verify(result[0][0] == 'mbuf_pool_socket_0', "dump mempool
> name failed")
>
> def test_physmem_dump(self):
> """
> --
> 1.9.3
next prev parent reply other threads:[~2017-08-14 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 8:25 lu,peipei
2017-08-14 8:53 ` Liu, Yong [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-15 5:13 lu,peipei
2017-08-14 6:31 lu,peipei
2017-08-11 6:03 lu,peipei
2017-08-11 7:11 ` 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=86228AFD5BCD8E4EBFD2B90117B5E81E62E530FC@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=peipeix.lu@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).