From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V3 1/6] tests/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp: update case code for dpdk code change
Date: Thu, 11 Nov 2021 11:05:20 +0800 [thread overview]
Message-ID: <1636599925-153067-1-git-send-email-songx.jiale@intel.com> (raw)
dpdk invalid port create rule echo change
According to dpdk commit 1179f05cc9a0.
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
| 2 +-
| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--git a/test_plans/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp_test_plan.rst b/test_plans/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp_test_plan.rst
index b9229f19..34f97ed9 100644
--- a/test_plans/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp_test_plan.rst
+++ b/test_plans/cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp_test_plan.rst
@@ -1142,7 +1142,7 @@ Subcase 5: invalid port
Failed to create flow, report message::
- No such device: No such device
+ Invalid port 1
2. check the rule list on port 0::
--git a/tests/TestSuite_cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp.py b/tests/TestSuite_cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp.py
index df2f8d58..02da01e0 100644
--- a/tests/TestSuite_cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp.py
+++ b/tests/TestSuite_cvl_advanced_iavf_rss_vlan_esp_ah_l2tp_pfcp.py
@@ -992,7 +992,7 @@ class Cvl_advance_iavf_rss_vlan_ah_l2tp_pfcp(TestCase):
def test_invalid_port(self):
rule = 'flow create 1 ingress pattern eth / ipv4 / udp / pfcp / end actions rss types pfcp end key_len 0 queues end / end'
- self.rsspro.create_rule(rule, check_stats=False, msg='No such device')
+ self.rsspro.create_rule(rule, check_stats=False, msg='Invalid port 1')
self.rsspro.check_rule(stats=False, rule_list=[rule])
pattern = 'Invalid port 1'
out = self.dut.send_command("flow list 1", timeout=1)
--
2.17.1
next reply other threads:[~2021-11-11 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 3:05 Jiale Song [this message]
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 ` [dts] [PATCH V3 5/6] test_plans/iavf_fdir: " Jiale Song
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:03 Jiale Song
2021-11-11 2:38 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-1-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).