From: Lijuan Tu <lijuan.tu@intel.com>
To: dts@dpdk.org, pmacarth@iol.unh.edu, alialnu@mellanox.com
Cc: Lijuan Tu <lijuan.tu@intel.com>
Subject: [dts] [next] [PATCH 0/3] support update-expected to meet Open Lab requirement
Date: Fri, 20 Jul 2018 23:22:01 +0800 [thread overview]
Message-ID: <1532100124-64769-1-git-send-email-lijuan.tu@intel.com> (raw)
The Linux Foundation's DPDK Project has established a DPDK Performance
Test Lab. It's specification require DTS to support an --update-expected
argument which will cause the script to update all expected values based
on the results of the current test run.
So far, single core performance test are deployed, and more test cases
will be deployed in future.
Current single core performance test script has many hardcode, remove
them and make it more easily to meet the DPDK Performance Test Lab
Specification.
Lijuan Tu (3):
framework: support argument: --update-expected.
tests/nic_single_core_perf: remove hardcode
conf/nic_single_core_perf: redefine elements
conf/nic_single_core_perf.cfg | 33 ++-
framework/config.py | 11 +
framework/dts.py | 6 +-
framework/main.py | 6 +-
framework/settings.py | 1 +
framework/test_case.py | 22 +-
tests/TestSuite_nic_single_core_perf.py | 374 ++++++++++++++++----------------
7 files changed, 256 insertions(+), 197 deletions(-)
--
1.8.3.1
next reply other threads:[~2018-07-20 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 15:22 Lijuan Tu [this message]
2018-07-20 15:22 ` [dts] [next] [PATCH 1/3] framework: support argument: --update-expected Lijuan Tu
2018-07-20 7:23 ` Liu, Yong
2018-07-20 15:22 ` [dts] [next] [PATCH 2/3] tests/nic_single_core_perf: remove hardcode Lijuan Tu
2018-07-20 15:22 ` [dts] [next] [PATCH 3/3] conf/nic_single_core_perf: redefine elements Lijuan Tu
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=1532100124-64769-1-git-send-email-lijuan.tu@intel.com \
--to=lijuan.tu@intel.com \
--cc=alialnu@mellanox.com \
--cc=dts@dpdk.org \
--cc=pmacarth@iol.unh.edu \
/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).