Skip to contentSkip to conversation

unit_tests_eal/link_bonding_rssconf: link_bonding_rssconf_autotest test failed

Bug 1056 [email protected] 1 participant 2 messages Jul 22, 2022 – Aug 5, 2022

lore
Share & tools
lore

[email protected]

author
#0 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=1056

            Bug ID: 1056
           Summary: [dpdk-19.11.13-rc1]
                    unit_tests_eal/link_bonding_rssconf:
                    link_bonding_rssconf_autotest test failed
           Product: DPDK
           Version: 19.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: [email protected]
          Reporter: [email protected]

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: 7.00 0x80004cf8 1.2063.0
driver: vfio-pci
kdriver: i40e-2.9.21

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(2629) - Failed to disable promiscuous mode for port 0: Operation not supported bond_ethdev_promiscuous_disable(2629) - Failed to disable promiscuous mode for port 1: Operation not supported bond_ethdev_promiscuous_disable(2629) - Failed to disable promiscuous mode for port 2: Operation not supported bond_ethdev_promiscuous_disable(2629) - Failed to disable promiscuous mode for port 3: Operation not supported bond_ethdev_allmulticast_disable(2775) - Failed to disable allmulti mode for port 0: Operation not supported bond_ethdev_allmulticast_disable(2775) - Failed to disable allmulti mode for port 1: Operation not supported bond_ethdev_allmulticast_disable(2775) - Failed to disable allmulti mode for port 2: Operation not supported bond_ethdev_allmulticast_disable(2775) - Failed to disable allmulti mode for port 3: Operation not supported
bond_ethdev_rss_hash_update(3084) - rss_key will be truncated bond_ethdev_rss_hash_update(3084) - rss_key will be truncated bond_ethdev_rss_hash_update(3084) - rss_key will be truncated bond_ethdev_rss_hash_update(3084) - rss_key will be truncated bond_ethdev_rss_hash_update(3084) - rss_key will be truncated bond_ethdev_rss_hash_update(3084) - rss_key will be truncated bond_ethdev_rss_hash_update(3084) - rss_key will be truncated bond_ethdev_rss_hash_update(3084) - rss_key will be truncated bond_ethdev_rss_hash_update(3084) - 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(2629) - Failed to disable promiscuous mode for port 0: Operation not supported bond_ethdev_promiscuous_disable(2629) - Failed to disable promiscuous mode for port 1: Operation not supported bond_ethdev_promiscuous_disable(2629) - Failed to disable promiscuous mode for port 2: Operation not supported bond_ethdev_promiscuous_disable(2629) - Failed to disable promiscuous mode for port 3: Operation not supported bond_ethdev_allmulticast_disable(2775) - Failed to disable allmulti mode for port 0: Operation not supported bond_ethdev_allmulticast_disable(2775) - Failed to disable allmulti mode for port 1: Operation not supported bond_ethdev_allmulticast_disable(2775) - Failed to disable allmulti mode for port 2: Operation not supported bond_ethdev_allmulticast_disable(2775) - Failed to disable allmulti mode for port 3: Operation not supported
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 530bf55366b6aa2859154add679fd01955280d02 (HEAD -> v19.11.13-rc1)

Author: Huisong Li <[email protected]>
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 <[email protected]>
Signed-off-by Dongdong Liu <[email protected]>
Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.