From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1070] [dpdk-20.11.6-rc1] unit_tests_eal/link_bonding_rssconf: link_bonding_rssconf_autotest test failed
Date: Mon, 22 Aug 2022 09:13:07 +0000 [thread overview]
Message-ID: <bug-1070-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1070
Bug ID: 1070
Summary: [dpdk-20.11.6-rc1]
unit_tests_eal/link_bonding_rssconf:
link_bonding_rssconf_autotest test failed
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: linglix.chen@intel.com
Target Milestone: ---
Environment
OS: Ubuntu 18.04.3 LTS/4.15.0-55-generic
Compiler: gcc version (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
NIC firmware: 8.00 0x80008c1a 1.2766.0
driver: vfio-pci
kdriver: i40e-2.14.13
Test Setup
1. launch testpmd
x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1,2,3,4 -n 4
2.start autotest
RTE>>link_bonding_rssconf_autotest
Show the output from the previous commands.
+ ------------------------------------------------------- +
+ Test Suite : RSS Dynamic Configuration for Bonding Unit Test Suite
+ ------------------------------------------------------- +
+ TestCase [ 0] : test_setup succeeded
Device with port_id=0 already stopped
Device with port_id=1 already stopped
Device with port_id=2 already stopped
Device with port_id=3 already stopped
bond_ethdev_promiscuous_disable(2669) - Failed to disable promiscuous mode for
port 0: Operation not supported
bond_ethdev_promiscuous_disable(2669) - Failed to disable promiscuous mode for
port 1: Operation not supported
bond_ethdev_promiscuous_disable(2669) - Failed to disable promiscuous mode for
port 2: Operation not supported
bond_ethdev_promiscuous_disable(2669) - Failed to disable promiscuous mode for
port 3: Operation not supported
bond_ethdev_allmulticast_disable(2815) - Failed to disable allmulti mode for
port 0: Operation not supported
bond_ethdev_allmulticast_disable(2815) - Failed to disable allmulti mode for
port 1: Operation not supported
bond_ethdev_allmulticast_disable(2815) - Failed to disable allmulti mode for
port 2: Operation not supported
bond_ethdev_allmulticast_disable(2815) - Failed to disable allmulti mode for
port 3: Operation not supported
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
bond_ethdev_rss_hash_update(3124) - rss_key will be truncated
Port 0 must be stopped to allow reset
Port 0 must be stopped to allow reset
Port 1 must be stopped to allow reset
Port 2 must be stopped to allow reset
Port 3 must be stopped to allow reset
+ TestCase [ 1] : test_rss succeeded
bond_ethdev_promiscuous_disable(2669) - Failed to disable promiscuous mode for
port 0: Operation not supported
bond_ethdev_promiscuous_disable(2669) - Failed to disable promiscuous mode for
port 1: Operation not supported
bond_ethdev_promiscuous_disable(2669) - Failed to disable promiscuous mode for
port 2: Operation not supported
bond_ethdev_promiscuous_disable(2669) - Failed to disable promiscuous mode for
port 3: Operation not supported
bond_ethdev_allmulticast_disable(2815) - Failed to disable allmulti mode for
port 0: Operation not supported
bond_ethdev_allmulticast_disable(2815) - Failed to disable allmulti mode for
port 1: Operation not supported
bond_ethdev_allmulticast_disable(2815) - Failed to disable allmulti mode for
port 2: Operation not supported
bond_ethdev_allmulticast_disable(2815) - Failed to disable allmulti mode for
port 3: Operation not supported
EAL: Test assert test_rss_config_lazy line 502 failed: Succeeded in setting
bonded port hash function
EAL: Test assert test_rss_lazy line 568 failed: Succeeded in setting RSS hash
when RX_RSS mq_mode is turned off
Port 0 must be stopped to allow reset
Port 1 must be stopped to allow reset
Port 2 must be stopped to allow reset
Port 3 must be stopped to allow reset
+ TestCase [ 2] : test_rss_lazy failed
Device with port_id=4 already stopped
+ ------------------------------------------------------- +
+ Test Suite Summary
+ Tests Total : 3
+ Tests Skipped : 0
+ Tests Executed : 3
+ Tests Unsupported: 0
+ Tests Passed : 2
+ Tests Failed : 1
+ ------------------------------------------------------- +
Test Failed
Expected Result
+ ------------------------------------------------------- +
+ Test Suite Summary : RSS Dynamic Configuration for Bonding Unit Test Suite
+ ------------------------------------------------------- +
+ Tests Total : 3
+ Tests Skipped : 0
+ Tests Executed : 3
+ Tests Unsupported: 0
+ Tests Passed : 3
+ Tests Failed : 0
+ ------------------------------------------------------- +
Test OK
Regression
Is this issue a regression: (Y/N)Y
Version the regression was introduced: Specify git id if known.
commit 1adbdac76c2277546bedfb664a37d6e7e5339721
Author: Huisong Li <lihuisong@huawei.com>
Date: Wed Jun 8 19:45:48 2022 +0800
test/bonding: fix RSS test when disable RSS
[ upstream commit 6496922368fe03be9ab4137f2d615dba1a766f39 ]
The "test_rss_lazy" test is used for testing bonding RSS functions
when bonded port disable RSS. Currently, this test case can update
RSS functions of bonded and slave port if bonded port turns off RSS.
It is unreasonable and has been adjusted to be non-updateable in
following patch:
"93e1ea6dfa99 ethdev: fix RSS update when RSS is disabled"
So this patch fixes this test code.
Fixes: 43b630244e7e ("app/test: add dynamic bonding RSS configuration")
Signed-off-by: Huisong Li <lihuisong@huawei.com>
Signed-off-by: Dongdong Liu <liudongdong3@huawei.com>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-08-22 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:13 bugzilla [this message]
2022-08-24 2:24 ` bugzilla
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=bug-1070-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).