[dpdk-dev] [Bug 827] unit_tests_eal/link_bonding:Failed to execute link_bonding_autotest

[bugzilla at dpdk.org]

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

            Bug ID: 827
           Summary: unit_tests_eal/link_bonding:Failed to execute
                    link_bonding_autotest
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev at dpdk.org
          Reporter: leweix.yang at intel.com
  Target Milestone: ---

DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
21.11.0-rc0:e0ae3db0c043cbdc4cc22bb60206f21ec4a82a02
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Red Hat Enterprise Linux 8.4 4.18.0-305.19.1.el8_4.x86_64 
Compiler: gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
Hardware platform:  Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz.
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
Device version: 2.17.1
NIC firmware: 8.30 0x8000a485 1.2926.0



Test Setup
Steps to reproduce
List the steps to reproduce the issue:

1. build dpdk 
# rm -rf x86_64-native-linuxapp-gcc
# CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib
-Dc_args='-DRTE_EAL_IGB_UIO=1' --default-library=static
x86_64-native-linuxapp-gcc 
# ninja -C x86_64-native-linuxapp-gcc -j 70 
2.lanch app
# ./x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1,2,3,4 -n 4  
--file-prefix=dpdk_4932_20211013214822
3.execute dpdk command
# link_bonding_autotest


Show the output from the previous commands:

+ ------------------------------------------------------- +
 + Test Suite Summary : Link Bonding Unit Test Suite
 + ------------------------------------------------------- +
 + Tests Total :       65
 + Tests Skipped :      0
 + Tests Executed :    65
 + Tests Unsupported:   0
 + Tests Passed :      17
 + Tests Failed :      48
 + ------------------------------------------------------- +
Test Failed



Expected Result
Explain what is the expected result in text or as an example output:

+ ------------------------------------------------------- +
 + Test Suite Summary : Link Bonding Unit Test Suite
 + ------------------------------------------------------- +
 + Tests Total :       65
 + Tests Skipped :      0
 + Tests Executed :    65
 + Tests Unsupported:   0
 + Tests Passed :      65
 + Tests Failed :       0
 + ------------------------------------------------------- +
Test OK



Regression
Is this issue a regression: Y

git show 7483341ae5533c5d5fa080a5d229e6f2daf03ea5
commit 7483341ae5533c5d5fa080a5d229e6f2daf03ea5 (HEAD, refs/bisect/bad)
Author: Xueming Li <xuemingl at nvidia.com>
Date: Wed Oct 6 19:18:22 2021 +0800

ethdev: change queue release callback

Currently, most ethdev callback API use queue ID as parameter, but Rx
and Tx queue release callback use queue object which is used by Rx and
Tx burst data plane callback.

To align with other eth device queue configuration callbacks:

queue release callbacks are changed to use queue ID
all drivers are adapted
Signed-off-by: Xueming Li <xuemingl at nvidia.com>
Reviewed-by: Andrew Rybchenko <andrew.rybchenko at oktetlabs.ru>
Acked-by: Ajit Khaparde <ajit.khaparde at broadcom.com>
Acked-by: Somnath Kotur <somnath.kotur at broadcom.com>
Acked-by: Ferruh Yigit <ferruh.yigit at intel.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.