From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V2 0/2] fix testplan issue and add automation
Date: Thu, 28 Apr 2022 07:40:37 +0000 [thread overview]
Message-ID: <20220428074037.42220-1-weix.ling@intel.com> (raw)
*** BLURB HERE ***
v1:
1.test_plans/vdev_primary_secondary_test_plan:
1)Fix testcase2 app name error issue.
2)Change testcase1 testpmd fwd mode from `set fwd txonly` and `start`
to `set fwd mac` and `start tx_first` take VM and testpmd can loop the
traffic.
2.tests/vdev_primary_secondary:
Add automation testcase2 sync with testplan and optimize code.
3.By DPDK-32213 bug, testcase2 will run FAILED before the bellow patch
merged into DPDK.
http://patchwork.dpdk.org/project/dpdk/patch/20220421111537.935333-1-yuanx.wang@intel.com/
v2:
Delete testcase1 step 1 `Bind one port to vfio-pci` because this case
no need to use port.
Wei Ling (2):
test_plans/vdev_primary_secondary_test_plan: fix testcase2 app name
error issue
tests/vdev_primary_secondary: add automation testcase2 sync with
testplan
.../vdev_primary_secondary_test_plan.rst | 15 +-
tests/TestSuite_vdev_primary_secondary.py | 148 +++++++++++-------
2 files changed, 104 insertions(+), 59 deletions(-)
--
2.34.1
reply other threads:[~2022-04-28 7:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220428074037.42220-1-weix.ling@intel.com \
--to=weix.ling@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).