From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1593] meson_tests/driver link_bonding_autotest test failed
Date: Mon, 09 Dec 2024 10:14:31 +0000 [thread overview]
Message-ID: <bug-1593-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2716 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1593
Bug ID: 1593
Summary: meson_tests/driver link_bonding_autotest test failed
Product: DPDK
Version: 22.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: 09fb920298 (tag: v22.11.7-rc1) version: 22.11.7-rc1
OS: openEuler 22.03/5.10.0-136.26.0.102.oe2203sp1.x86_64
Compiler: gcc version 10.3.1 (GCC)
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
NIC firmware:
FW: 9.00 0x8000ceba 1.1691.0
Driver: i40e-2.20.12
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. Start link_bonding_autotest test
meson test -C x86_64-native-linuxapp-gcc --suite DPDK:driver-tests
link_bonding_autotest -t 24 --test-args '-c 0xff' --num-processes 20
Show the output from the previous commands.
===========================================
ninja: no work to do.
ninja: Entering directory `/root/dpdk/x86_64-native-linuxapp-gcc'
ninja: no work to do.
1/1 DPDK:driver-tests / link_bonding_autotest FAIL 3.05s
(exit status 255 or signal 127 SIGinvalid)
>>> MALLOC_PERTURB_=156 DPDK_TEST=link_bonding_autotest
>>> /root/dpdk/x86_64-native-linuxapp-gcc/app/test/dpdk-test -c 0xff
Ok: 0
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 0
Timeout: 0
Full log written to
/root/dpdk/x86_64-native-linuxapp-gcc/meson-logs/testlog.txt
Expected Result
===============
Test OK, no fail
bad commit
**********
commit 634cf74378ab4fb451ea6f24aca1658cfce24743
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: 4962 bytes --]
next reply other threads:[~2024-12-09 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 10:14 bugzilla [this message]
2024-12-11 8:33 ` [DPDK/meson Bug 1593] [dpdk-22.11.7-rc1]meson_tests/driver link_bonding_autotest test failed 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-1593-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.