From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1594] [dpdk-21.11.9-rc1] unit_tests_eal/link_bonding: link_bonding_autotest test failed
Date: Wed, 11 Dec 2024 07:58:37 +0000 [thread overview]
Message-ID: <bug-1594-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2984 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1594
Bug ID: 1594
Summary: [dpdk-21.11.9-rc1] unit_tests_eal/link_bonding:
link_bonding_autotest test failed
Product: DPDK
Version: 21.11
Hardware: x86
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: linglix.chen@intel.com
Target Milestone: ---
Environment
===========
DPDK version: f197f1e13c (version: 21.11.9-rc1）
OS: Red Hat Enterprise Linux 8.4 (Ootpa)/4.18.0-305.19.1.el8_4.x86_64
Compiler: gcc version 8.4.1 20200928
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
NIC firmware:
FW: 8.30 0x8000a485 1.2926.0
Driver: i40e-2.17.4
Test Setup
Steps to reproduce
==================
1. Bind ports to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:af:00.0 0000:af:00.1
2. Launch dpdk-test
x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1-4 -n 4 -a 0000:af:00.0 -a
0000:af:00.1
3. Start link_bonding_autotest test
RTE>>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 : 27
+ Tests Failed : 38
+ ------------------------------------------------------- +
Test Failed
Expected Result
===============
+ ------------------------------------------------------- +
+ 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
bad commit
**********
commit e1a999e7ff4cf08e5393ce7c1a7873bc8f7233ff
Author: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu Nov 21 10:23:22 2024 -0800
test/bonding: fix loop on members
[ upstream commit 112ce3917674b7e316776305d7e27778d17eb1b7 ]
Do not use same variable for outer and inner loop in bonding test.
Since the loop is just freeing the resulting burst use bulk free.
Link: https://pvs-studio.com/en/blog/posts/cpp/1179/
Fixes: 92073ef961ee ("bond: unit tests")
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5198 bytes --]
next reply other threads:[~2024-12-11 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 7:58 bugzilla [this message]
2024-12-11 8:33 ` 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-1594-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).