From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1972] telemetry_all test times out
Date: Wed, 22 Jul 2026 17:58:25 +0000 [thread overview]
Message-ID: <bug-1972-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1972
Bug ID: 1972
Summary: telemetry_all test times out
Product: DPDK
Version: 26.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Running fast-tests on 26.07 has one failure.
Running test standalone, and it regularly takes over 10 seconds.
114/114 fast-tests - DPDK:telemetry_all
TIMEOUT 10.01s killed by signal 15 SIGTERM
>>>
>>> UBSAN_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
>>> MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
>>> MESON_TEST_ITERATION=1 MALLOC_PERTURB_=247
>>> /home/shemminger/DPDK/bpf/app/test/suites/test_telemetry.sh app/dpdk-test
>>> --no-huge -m 2048 --vdev=crypto_null0 --vdev=dma_skeleton0
>>> --vdev=event_skeleton0 --vdev=net_null0 --vdev=rawdev_skeleton0 -a
>>> 0000:00:00.0
Ok: 110
Fail: 0
Skipped: 3
Timeout: 1
testlog.txt
================================== 151/151 ===================================
test: fast-tests - DPDK:telemetry_all
start time: 17:56:44
duration: 10.01s
result: killed by signal 15 SIGTERM
command:
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
MALLOC_PERTURB_=175
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
MESON_TEST_ITERATION=1
/home/shemminger/DPDK/main/app/test/suites/test_telemetry.sh app/dpdk-test
--no-huge -m 2048 --vdev=crypto_null0 --vdev=dma_skeleton0
--vdev=event_skeleton0 --vdev=net_null0 --vdev=rawdev_skeleton0 -a 0000:00:00.0
----------------------------------- stdout -----------------------------------
/usr/bin/jq
RTE>>
----------------------------------- stderr -----------------------------------
EAL: Detected CPU lcores: 32
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
CRYPTODEV: Creating cryptodev crypto_null0
CRYPTODEV: Initialisation parameters - name: crypto_null0,socket id: 0, max
queue pairs: 8
SKELDMA: skeldma_probe(): Create dma_skeleton0 dmadev with lcore-id -1
SKELETON_PMD: skeleton_rawdev_probe(): Init rawdev_skeleton0 on NUMA node 0
APP: HPET is not enabled, using TSC as default timer
ETHDEV: Failed to get dcb info, ret = -95
ETHDEV: Failed to get flow ctrl info, ret = -95
ETHDEV: Operation not supported by device
ETHDEV: Failed to get device reg info: -95
ETHDEV: Rx queue 0 of device with port_id=0 has not been setup
ETHDEV: error: Function not implemented, error type: 1
ETHDEV: Tx queue 0 of device with port_id=0 has not been setup
EVENTDEV: handle_rxa_get_queue_conf() line 3846: Invalid eth Rx adapter token
EVENTDEV: handle_rxa_get_queue_stats() line 3917: Invalid eth Rx adapter token
EVENTDEV: handle_rxa_queue_stats_reset() line 3986: Invalid eth Rx adapter
token
EVENTDEV: handle_rxa_instance_get() line 4048: Invalid eth Rx adapter token
EVENTDEV: handle_rxa_stats() line 3777: Failed to get Rx adapter stats
EVENTDEV: handle_rxa_stats_reset() line 3816: Failed to reset Rx adapter stats
EVTIM: EVTIMER: handle_ta_info() line 1413: Invalid timer adapter id 0
EVTIM: EVTIMER: handle_ta_stats() line 1458: Invalid timer adapter id 0
==============================================================================
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-07-22 17:58 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-1972-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.