From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V2 3/6] tests/cvl_fdir: update case code for dpdk code change
Date: Wed, 3 Nov 2021 10:59:03 +0800 [thread overview]
Message-ID: <1635908346-165194-3-git-send-email-songx.jiale@intel.com> (raw)
In-Reply-To: <1635908346-165194-1-git-send-email-songx.jiale@intel.com>
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
test_plans/cvl_fdir_test_plan.rst | 4 ++--
tests/TestSuite_cvl_fdir.py | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/test_plans/cvl_fdir_test_plan.rst b/test_plans/cvl_fdir_test_plan.rst
index b5052578..8e508d71 100644
--- a/test_plans/cvl_fdir_test_plan.rst
+++ b/test_plans/cvl_fdir_test_plan.rst
@@ -703,7 +703,7 @@ Note: there may be error message change.
get the message::
- No such device: No such device
+ Invalid port 2
10. check the flow list::
@@ -3550,7 +3550,7 @@ Subcase 11: invalid port
Failed to create flow, report message::
- No such device: No such device
+ Invalid port 2
2. check there is no rule listed on port 2::
diff --git a/tests/TestSuite_cvl_fdir.py b/tests/TestSuite_cvl_fdir.py
index 75c3ba93..d0ed03bc 100644
--- a/tests/TestSuite_cvl_fdir.py
+++ b/tests/TestSuite_cvl_fdir.py
@@ -2759,7 +2759,7 @@ class TestCVLFdir(TestCase):
# check_stats=False, check_msg='Bad arguments')
self.validate_fdir_rule(
'flow validate 2 ingress pattern eth / ipv4 src is 192.168.0.20 dst is 192.168.0.21 proto is 255 ttl is 2 tos is 4 / end actions queue index 1 / end',
- check_stats=False, check_msg='No such device')
+ check_stats=False, check_msg='Invalid port 2')
self.check_fdir_rule(stats=False)
def test_mac_ipv4_pay_protocal(self):
@@ -2980,7 +2980,7 @@ class TestCVLFdir(TestCase):
def test_invalid_port(self):
rule = "flow create 2 ingress pattern eth dst is 00:11:22:33:44:55 / ipv4 src is 192.168.0.20 dst is 192.168.0.21 / end actions queue index 1 / end"
- self.create_fdir_rule(rule, check_stats=False, msg="No such device: No such device")
+ self.create_fdir_rule(rule, check_stats=False, msg="Invalid port 2")
out = self.pmd_output.execute_cmd("flow list 2")
self.verify("Invalid port 2" in out, "expect Invalid port 2 in %s" % out)
--
2.17.1
next prev parent reply other threads:[~2021-11-03 2:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 2:59 [dts] [PATCH V2 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-03 2:59 ` [dts] [PATCH V2 2/6] tests/cvl_advanced_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-03 2:59 ` Jiale Song [this message]
2021-11-03 2:59 ` [dts] [PATCH V2 4/6] tests/flow_classify_softnic: " Jiale Song
2021-11-03 2:59 ` [dts] [PATCH V2 5/6] tests/update " Jiale Song
2021-11-03 2:59 ` [dts] [PATCH V2 6/6] tests/cvl_switch_filter_pppoe: update " Jiale Song
-- strict thread matches above, loose matches on Subject: below --
2021-11-09 9:40 [dts] [PATCH V2 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-09 9:40 ` [dts] [PATCH V2 3/6] tests/cvl_fdir: " Jiale Song
2021-11-03 3:12 [dts] [PATCH V2 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-03 3:12 ` [dts] [PATCH V2 3/6] tests/cvl_fdir: " Jiale Song
2021-11-03 2:49 [dts] [PATCH V2 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: " Jiale Song
2021-11-03 2:49 ` [dts] [PATCH V2 3/6] tests/cvl_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=1635908346-165194-3-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).