test suite reviews and discussions
 help / color / mirror / Atom feed
From: Lijuan Tu <lijuan.tu@intel.com>
To: dts@dpdk.org
Cc: Lijuan Tu <lijuan.tu@intel.com>
Subject: [dts] [next] [PATCH V3 0/3] support update-expected to meet Open Lab requirement
Date: Tue, 24 Jul 2018 18:20:02 +0800	[thread overview]
Message-ID: <1532427605-127449-1-git-send-email-lijuan.tu@intel.com> (raw)

The Linux Foundation's DPDK Project has established a DPDK Performance
Test Lab. Its specification requires 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 has been deployed, and more test cases
will be deployed in future.

Currently single core performance test script has many hardcode, remove
them and make it more appropriate 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           |  37 +++-
 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 | 378 ++++++++++++++++----------------
 7 files changed, 264 insertions(+), 197 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2018-07-24  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 10:20 Lijuan Tu [this message]
2018-07-24 10:20 ` [dts] [next] [PATCH V3 1/3] framework: support argument: --update-expected Lijuan Tu
2018-07-24 10:20 ` [dts] [next] [PATCH V3 2/3] tests/nic_single_core_perf: remove hardcode Lijuan Tu
2018-07-24 10:20 ` [dts] [next] [PATCH V3 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=1532427605-127449-1-git-send-email-lijuan.tu@intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    /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).