From: Haiyang Zhao <haiyangx.zhao@intel.com>
To: dts@dpdk.org
Cc: Haiyang Zhao <haiyangx.zhao@intel.com>
Subject: [dts] [PATCH V1 06/14] test_plans/iavf_package_driver_error_handle: fix build warnings and errors
Date: Tue, 23 Jun 2020 10:21:33 +0800 [thread overview]
Message-ID: <1592878901-216102-7-git-send-email-haiyangx.zhao@intel.com> (raw)
In-Reply-To: <1592878901-216102-1-git-send-email-haiyangx.zhao@intel.com>
Signed-off-by: Haiyang Zhao <haiyangx.zhao@intel.com>
---
test_plans/iavf_package_driver_error_handle_test_plan.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/test_plans/iavf_package_driver_error_handle_test_plan.rst b/test_plans/iavf_package_driver_error_handle_test_plan.rst
index 7294258..23978ea 100644
--- a/test_plans/iavf_package_driver_error_handle_test_plan.rst
+++ b/test_plans/iavf_package_driver_error_handle_test_plan.rst
@@ -87,6 +87,7 @@ Expected output in ctreat result::
The rule create should fail and with cause with below
iavf_flow_create(): Failed to create flow
port_flow_complain(): Caught PMD error type 2 (flow rule (handle)): Failed to create parser engine.: Invalid argument
+
Note. the rule should create fail, because the rule should does not support in old driver version.
Test Case 2: Check latst driver and invalid commes pkg compatibility
@@ -101,5 +102,6 @@ Test Case 2: Check latst driver and invalid commes pkg compatibility
Expected output in VF start result::
echo 1 > /sys/bus/pci/devices/0000\:b1\:00.0/sriov_numvfs
- -bash: echo: write error: Operation not supported
+ -bash: echo: write error: Operation not supported
+
Note. the error log is expected, because the vf does not support invalid commes pkg.
--
1.8.3.1
next prev parent reply other threads:[~2020-06-23 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 2:21 [dts] [PATCH V1 00/14] test_plans: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 01/14] test_plans/cvl_advanced_iavf_rss: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 02/14] test_plans/cvl_fdir: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 03/14] test_plans/fortville_rss_input: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 04/14] test_plans/generic_flow_api: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 05/14] test_plans/iavf_fdir: " Haiyang Zhao
2020-06-23 2:21 ` Haiyang Zhao [this message]
2020-06-23 2:21 ` [dts] [PATCH V1 07/14] test_plans/l2tp_esp_coverage: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 08/14] test_plans/loopback_virtio_user_server_mode: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 09/14] test_plans/pvp_multi_paths_performance: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 10/14] test_plans/pvp_multi_paths_virtio_single_core_performance: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 11/14] test_plans/rss_to_rte_flow: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 12/14] test_plans/stats_checks: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 13/14] test_plans/vm2vm_virtio_net_perf: " Haiyang Zhao
2020-06-23 2:21 ` [dts] [PATCH V1 14/14] test_plans/index: " Haiyang Zhao
2020-06-28 6:44 ` [dts] [PATCH V1 00/14] test_plans: " Tu, Lijuan
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=1592878901-216102-7-git-send-email-haiyangx.zhao@intel.com \
--to=haiyangx.zhao@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).