From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V3 5/6] test_plans/iavf_fdir: update case code for dpdk code change
Date: Thu, 11 Nov 2021 11:05:24 +0800 [thread overview]
Message-ID: <1636599925-153067-5-git-send-email-songx.jiale@intel.com> (raw)
In-Reply-To: <1636599925-153067-1-git-send-email-songx.jiale@intel.com>
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
test_plans/iavf_fdir_test_plan.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/test_plans/iavf_fdir_test_plan.rst b/test_plans/iavf_fdir_test_plan.rst
index 784392e2..8ffcab41 100644
--- a/test_plans/iavf_fdir_test_plan.rst
+++ b/test_plans/iavf_fdir_test_plan.rst
@@ -1239,7 +1239,7 @@ Note: some of the error messages may be differernt.
get the message::
- No such device: No such device
+ Invalid port 1
11. check the flow list::
@@ -4325,7 +4325,7 @@ Subcase 9: delete a non-existent rule
flush rules of port 1::
testpmd> flow flush 1
- port_flow_complain(): Caught PMD error type 1 (cause unspecified): No such device: No such device
+ Invalid port 1
Subcase 10: unsupported input set field
---------------------------------------
@@ -4395,7 +4395,7 @@ Subcase 13: invalid port
Failed to create flow, report message::
- No such device: No such device
+ Invalid port 1
2. check there is no rule listed on port 0,
check on port 1::
--
2.17.1
next prev parent reply other threads:[~2021-11-11 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 3:05 [dts] [PATCH V3 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-11 3:05 ` [dts] [PATCH V3 2/6] tests/cvl_advanced_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-11 3:05 ` [dts] [PATCH V3 3/6] tests/cvl_fdir: " Jiale Song
2021-11-11 3:05 ` [dts] [PATCH V3 4/6] tests/flow_classify_softnic: " Jiale Song
2021-11-11 3:05 ` Jiale Song [this message]
2021-11-11 3:05 ` [dts] [PATCH V3 6/6] test_plans/cvl_switch_filter_pppoe: " Jiale Song
-- strict thread matches above, loose matches on Subject: below --
2021-11-11 5:05 [dts] [PATCH V3 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-11 5:05 ` [dts] [PATCH V3 5/6] test_plans/iavf_fdir: " Jiale Song
2021-11-11 2:38 [dts] [PATCH V3 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-11 2:38 ` [dts] [PATCH V3 5/6] test_plans/iavf_fdir: " Jiale Song
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=1636599925-153067-5-git-send-email-songx.jiale@intel.com \
--to=songx.jiale@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).