From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Rami Rosen <ramirose@gmail.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] test_plans/telemetry: use correct name of script
Date: Tue, 23 Apr 2019 20:18:52 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA6580E@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190421140215.6207-1-ramirose@gmail.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Rami Rosen
> Sent: Sunday, April 21, 2019 7:02 AM
> To: dts@dpdk.org
> Cc: Rami Rosen <ramirose@gmail.com>
> Subject: [dts] [PATCH] test_plans/telemetry: use correct name of script
>
> This patch fixes the telemetry test plan to use the correct name of the
> usertools script, dpdk-telemetry-client.py.
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
> test_plans/telemetry_test_plan.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/test_plans/telemetry_test_plan.rst
> b/test_plans/telemetry_test_plan.rst
> index 1085fd5..4098683 100644
> --- a/test_plans/telemetry_test_plan.rst
> +++ b/test_plans/telemetry_test_plan.rst
> @@ -72,7 +72,7 @@ Prerequisites
>
> 4. Launch the ``telemetry`` python script with a client filepath :
>
> - python usertools/telemetry_client.py /var/run/some_client
> + python usertools/dpdk-telemetry-client.py /var/run/some_client
>
> 5. Build should include both make and mesion static/shared
>
> @@ -115,7 +115,7 @@ Test case: Stats of 2 ports for testpmd and telemetry
> with same type nic
>
> 3.Run Python terminal:
>
> - python ./usertools/telemetry_client.py
> + python ./usertools/dpdk-telemetry-client.py
> enter 1/2/ :
>
> 4.check and verify any error show on testpmd @@ -146,7 +146,7 @@ Test
> case: Stats of 2 ports for testpmd and telemetry with different type nic
>
> 3.Run Python terminal:
>
> - python ./usertools/telemetry_client.py
> + python ./usertools/dpdk-telemetry-client.py
> enter 1/2/ :
>
> 4.check and verify any error show on testpmd @@ -177,7 +177,7 @@ Test
> case: Stats of 4 ports for testpmd and telemetry with same type nic
>
> 3.Run Python terminal:
>
> - python ./usertools/telemetry_client.py
> + python ./usertools/dpdk-telemetry-client.py
> enter 1/2/
>
> 4.check and verify any error show on testpmd @@ -208,7 +208,7 @@ Test
> case: Stats of 4 ports for testpmd and telemetry with different type nic
>
> 3.Run Python terminal:
>
> - python ./usertools/telemetry_client.py
> + python ./usertools/dpdk-telemetry-client.py
> enter 1/2/ :
>
> 4.check and verify any error show on testpmd
> --
> 2.17.1
prev parent reply other threads:[~2019-04-23 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 14:02 Rami Rosen
2019-04-23 20:18 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BA6580E@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).