From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Rami Rosen <ramirose@gmail.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] tests/TestSuite_vhost_pmd_xstats: fix typos
Date: Tue, 26 Feb 2019 02:55:15 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA2719A@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1549865130-50670-1-git-send-email-ramirose@gmail.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Rami Rosen
> Sent: Monday, February 11, 2019 2:06 PM
> To: dts@dpdk.org
> Cc: Rami Rosen <ramirose@gmail.com>
> Subject: [dts] [PATCH] tests/TestSuite_vhost_pmd_xstats: fix typos
>
> This patch fixes typos in TestSuite_vhost_pmd_xstats:
> 1) In test_stability(), the time interval of the test should be
> 30 minutes instead of 2 minutes.
> 2) Xstats should be xstats (to be consistent with the rest of this module)
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
> tests/TestSuite_vhost_pmd_xstats.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-) mode change 100644 => 100755
> tests/TestSuite_vhost_pmd_xstats.py
>
> diff --git a/tests/TestSuite_vhost_pmd_xstats.py
> b/tests/TestSuite_vhost_pmd_xstats.py
> old mode 100644
> new mode 100755
> index c65f824..e33b342
> --- a/tests/TestSuite_vhost_pmd_xstats.py
> +++ b/tests/TestSuite_vhost_pmd_xstats.py
> @@ -208,7 +208,7 @@ class TestVhostPmdXstats(TestCase):
> def test_stability(self):
> """
> Verify stability case with multiple queues for Vhost PMD xstats
> - Send packets for 30 minutes, check the Xstats still can work correctly
> + Send packets for 2 minutes, check the xstats still can work
> + correctly
> """
> self.scapy_num = 0
> self.prepare_start()
> --
> 1.8.3.1
next prev parent reply other threads:[~2019-02-26 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 6:05 Rami Rosen
2019-02-26 2:55 ` Tu, Lijuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-19 12:47 Rami Rosen
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=8CE3E05A3F976642AAB0F4675D0AD20E0BA2719A@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=ramirose@gmail.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).