From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>,
"Wang, Yinan" <yinan.wang@intel.com>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V2 0/4] metrics: upload suite test plan and script
Date: Thu, 2 Jan 2020 03:19:46 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBA0E4B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191213085140.13231-1-yufengx.mo@intel.com>
Applied the series.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Friday, December 13, 2019 4:52 PM
> To: dts@dpdk.org; Wang, Yinan <yinan.wang@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V2 0/4] metrics: upload suite test plan and script
>
>
> v2:
> - update latencystat and bit rate option.
> - add ewma_bits_out/in check.
> - use new pktgen methods as traffic policy mode testing packet generator.
> - abandon non-blocked ixia traffic source code changes in framework.
> - use pktgen callback to to take the place of non-blocked query method.
> - display metrics data and save them into rst file.
> - use suite configuration file to set test content.
> - remove debug source code.
> - fix typo issue.
> - fix pep8 issue.
>
> yufengmx (4):
> conf/metrics: test configuration
> test_plans/metrics: add test plan index
> test_plans/metrics: upload test plan
> tests/metrics: upload automation script
>
> conf/metrics.cfg | 5 +
> test_plans/index.rst | 1 +
> test_plans/metrics_test_plan.rst | 236 +++++++++
> tests/TestSuite_metrics.py | 824 +++++++++++++++++++++++++++++++
> 4 files changed, 1066 insertions(+)
> create mode 100644 conf/metrics.cfg
> create mode 100644 test_plans/metrics_test_plan.rst create mode 100644
> tests/TestSuite_metrics.py
>
> --
> 2.21.0
prev parent reply other threads:[~2020-01-02 3:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 8:51 yufengmx
2019-12-13 8:51 ` [dts] [PATCH V2 1/4] conf/metrics: test configuration yufengmx
2019-12-27 8:32 ` Wang, Yinan
2019-12-13 8:51 ` [dts] [PATCH V2 2/4] test_plans/metrics: add test plan index yufengmx
2019-12-27 8:32 ` Wang, Yinan
2019-12-13 8:51 ` [dts] [PATCH V2 3/4] test_plans/metrics: upload test plan yufengmx
2019-12-27 8:32 ` Wang, Yinan
2019-12-13 8:51 ` [dts] [PATCH V2 4/4] tests/metrics: upload automation script yufengmx
2019-12-27 8:32 ` Wang, Yinan
2019-12-27 8:32 ` [dts] [PATCH V2 0/4] metrics: upload suite test plan and script Wang, Yinan
2020-01-02 3:19 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BBA0E4B@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yinan.wang@intel.com \
--cc=yufengx.mo@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).