From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1469] [dpdk-24.07] meson_tests/driver-tests: event_dma_adapter_autotest test timeout
Date: Fri, 21 Jun 2024 09:27:09 +0000 [thread overview]
Message-ID: <bug-1469-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 4060 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1469
Bug ID: 1469
Summary: [dpdk-24.07] meson_tests/driver-tests:
event_dma_adapter_autotest test timeout
Product: DPDK
Version: 24.07
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: songx.jiale@intel.com
Target Milestone: ---
[Environment]
DPDK version:
dpdk-24.07.0-rc1: 4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f
Other software versions: N/A.
OS: Ubuntu 24.04 LTS/6.8.0-31-generic
Compiler: gcc version 8.5.0 20210514
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: Intel Corporation Ethernet Controller E810-C for SFP [8086:1593]
(rev 01)
NIC driver: ice-1.14.9
NIC firmware: 4.50 0x8001d8f0 1.3597.0
[Test Setup]
1.blind port to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:18:00.0 0000:18:00.1 0000:18:00.2
0000:18:00.3
2. start meson_tests
meson test -C x86_64-native-linuxapp-gcc --suite DPDK:driver-tests
event_dma_adapter_autotest -t 24 --num-processes 20 --test-args '-c 0xff
--vdev=dma_skeleton -a 0000:18:00.0 -a 0000:18:00.1 -a 0000:18:00.2 -a
0000:18:00.3'
[Show the output from the previous commands.]
ninja: Entering directory `/root/dpdk/x86_64-native-linuxapp-gcc'
ninja: no work to do.
WARNING: CTRL-C detected, interrupting DPDK:driver-tests /
event_dma_adapter_autotest
1/1 DPDK:driver-tests / event_dma_adapter_autotest INTERRUPT
5.91s killed by signal 15 SIGTERM
>>> MALLOC_PERTURB_=4
>>> 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
>>> DPDK_TEST=event_dma_adapter_autotest
>>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
>>> /root/dpdk/x86_64-native-linuxapp-gcc/app/dpdk-test -c 0xff
>>> --vdev=dma_skeleton -a 0000:18:00.0 -a 0000:18:00.1 -a 0000:18:00.2 -a
>>> 0000:18:00.3
Ok: 0
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 0
Timeout: 1
[Expected Result]
ninja: Entering directory `/root/dpdk/x86_64-native-linuxapp-gcc'
ninja: no work to do.
WARNING: CTRL-C detected, interrupting DPDK:driver-tests /
event_dma_adapter_autotest
1/1 DPDK:driver-tests / event_dma_adapter_autotest INTERRUPT
5.91s killed by signal 15 SIGTERM
>>> MALLOC_PERTURB_=4
>>> 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
>>> DPDK_TEST=event_dma_adapter_autotest
>>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
>>> /root/dpdk/x86_64-native-linuxapp-gcc/app/dpdk-test -c 0xff
>>> --vdev=dma_skeleton -a 0000:18:00.0 -a 0000:18:00.1 -a 0000:18:00.2 -a
>>> 0000:18:00.3
Ok: 1
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 0
Timeout: 0
[Regression]
Is this issue a regression: (Y/N) Y
commit 588dcac2361011556934166d93da62dae712ce69
Author: Pavan Nikhilesh <pbhagavatula@marvell.com>
Date: Fri Jun 7 16:06:25 2024 +0530
eventdev/dma: reorganize event DMA ops
Re-organize event DMA ops structure to allow holding
source and destination pointers without the need for
additional memory, the mempool allocating memory for
rte_event_dma_adapter_ops can size the structure to
accommodate all the needed source and destination
pointers.
Add multiple words for holding user metadata, adapter
implementation specific metadata and event metadata.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Acked-by: Amit Prakash Shukla <amitprakashs@marvell.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 6329 bytes --]
reply other threads:[~2024-06-21 9:27 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-1469-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).