From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1967] [dpdk-26.07] ABI testing dpdk26.07+dpdk25.11 meson_tests/test_fasts vdev_autotest and devargs_autotest both failed
Date: Tue, 14 Jul 2026 09:35:00 +0000 [thread overview]
Message-ID: <bug-1967-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1967
Bug ID: 1967
Summary: [dpdk-26.07] ABI testing dpdk26.07+dpdk25.11
meson_tests/test_fasts vdev_autotest and
devargs_autotest both failed
Product: DPDK
Version: 26.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: yux.jiang@intel.com
Target Milestone: ---
Environment
-----------
DPDK version:
[DPDK 26.07rc3]
Steps to reproduce
------------------
1, Build latest dpdk(dpdk26.07rc3)
cd dpdk
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Dlibdir=lib -Dc_args=-DRTE_BUILD_SHARED_LIB
--default-library=shared x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
rm -rf /root/tmp/dpdk_share_lib /root/shared_lib_dpdk
DESTDIR=/root/tmp/dpdk_share_lib ninja -C x86_64-native-linuxapp-gcc -j 110
install
mv /root/tmp/dpdk_share_lib/usr/local/lib /root/shared_lib_dpdk
cat /root/.bashrc | grep LD_LIBRARY_PATH
sed -i 's#export LD_LIBRARY_PATH=.*#export
LD_LIBRARY_PATH=/root/shared_lib_dpdk#g' /root/.bashrc
2, copy LTS(dpdk25.11) dpdk_abi.tar.gz and build LTS dpdk
tar zxf /tmp/dpdk_abi.tar.gz -C ~
cd ~/dpdk/
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Dlibdir=lib -Dc_args=-DRTE_BUILD_SHARED_LIB
--default-library=shared x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
rm -rf x86_64-native-linuxapp-gcc/lib
rm -rf x86_64-native-linuxapp-gcc/drivers
3, do meson test
meson test -C x86_64-native-linuxapp-gcc --suite DPDK:fast-tests
devargs_autotest vdev_autotest -t 24 --num-processes 20 --test-args '-l 1-8 -d
/root/shared_lib_dpdk'
Show the output from the previous commands.
-------------------------------------------
FAIL
root@icx-jy-abi-d81:~/dpdk# MALLOC_PERTURB_=132
LD_LIBRARY_PATH=/root/dpdk/x86_64-native-linuxapp-gcc/lib:/root/dpdk/x86_64-native-linuxapp-gcc/drivers:/root/shared_lib_dpdk
MESON_TEST_ITERATION=1 DPDK_TEST=vdev_autotest
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
/root/dpdk/x86_64-native-linuxapp-gcc/app/dpdk-test --no-huge -m 2048 -d
/root/dpdk/x86_64-native-linuxapp-gcc/drivers -l 1-8 -d /root/shared_lib_dpdk
EAL: Detected CPU lcores: 160
EAL: Detected NUMA nodes: 2
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
APP: HPET is not enabled, using TSC as default timer
RTE>>vdev_autotest
== test vdev bus ==
Segmentation fault (core dumped)
Expected Result
---------------
Test OK
Is this issue a regression: Y
-----------------------------
devargs_autotest bad commit: d03dbd4003 bus: support multiple probe
vdev_autotest bad commit: 89127f66f5 bus: consolidate device lookup
Need fix or not? pls confirm
----------------------------
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-07-14 9:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1967-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