From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: pbhagavatula@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw153525 [25.11 PATCH v2 5/5] eventdev: refactor DMA adapter ops
Date: Mon, 19 May 2025 16:03:09 -0400 [thread overview]
Message-ID: <20250519200309.44925-1-robot@bytheb.org> (raw)
In-Reply-To: <20250519185604.5584-6-pbhagavatula@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/153525/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15121104363
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
[1874/1953] Linking target app/dpdk-pdump
[1875/1953] Linking target app/dpdk-graph
[1876/1953] Linking target app/dpdk-test-acl
[1877/1953] Linking target app/dpdk-proc-info
[1878/1953] Linking target app/dpdk-test-cmdline
[1879/1953] Linking target app/dpdk-test-bbdev
[1880/1953] Linking target app/dpdk-test-crypto-perf
[1881/1953] Linking target app/dpdk-test-compress-perf
[1882/1953] Linking target app/dpdk-test-dma-perf
FAILED: app/dpdk-test-dma-perf
gcc -o app/dpdk-test-dma-perf app/dpdk-test-dma-perf.p/test-dma-perf_main.c.o app/dpdk-test-dma-perf.p/test-dma-perf_benchmark.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--no-as-needed -pthread -Wl,--start-group -lm -ldl -lnuma -lfdt '-Wl,-rpath,$ORIGIN/../lib:XXXXXXXXXXXXXXX' -Wl,-rpath-link,/home/runner/work/dpdk/dpdk/build/lib lib/librte_dmadev.so.25.2 lib/librte_eal.so.25.2 lib/librte_kvargs.so.25.2 lib/librte_log.so.25.2 lib/librte_telemetry.so.25.2 lib/librte_mbuf.so.25.2 lib/librte_mempool.so.25.2 lib/librte_ring.so.25.2 lib/librte_cfgfile.so.25.2 /usr/lib/x86_64-linux-gnu/libbsd.so /usr/lib/x86_64-linux-gnu/libarchive.so -Wl,--end-group
/usr/bin/ld: app/dpdk-test-dma-perf.p/test-dma-perf_benchmark.c.o: warning: relocation against `__rte_dma_trace_enqueue_ops' in read-only section `.text'
/usr/bin/ld: app/dpdk-test-dma-perf.p/test-dma-perf_benchmark.c.o: in function `rte_dma_trace_enqueue_ops':
/home/runner/work/dpdk/dpdk/build/../lib/dmadev/rte_dmadev_trace_fp.h:128: undefined reference to `__rte_dma_trace_enqueue_ops'
/usr/bin/ld: app/dpdk-test-dma-perf.p/test-dma-perf_benchmark.c.o: in function `rte_dma_trace_dequeue_ops':
/home/runner/work/dpdk/dpdk/build/../lib/dmadev/rte_dmadev_trace_fp.h:138: undefined reference to `__rte_dma_trace_dequeue_ops'
/usr/bin/ld: warning: creating DT_TEXTREL in a PIE
collect2: error: ld returned 1 exit status
[1883/1953] Linking target app/dpdk-test-fib
[1884/1953] Linking target app/dpdk-test-eventdev
[1885/1953] Linking target app/dpdk-test-flow-perf
[1886/1953] Linking target app/dpdk-test-gpudev
[1887/1953] Linking target app/dpdk-test-mldev
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2025-05-19 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250519185604.5584-6-pbhagavatula@marvell.com>
2025-05-19 18:31 ` |SUCCESS| pw153521-153525 " qemudev
2025-05-19 18:35 ` qemudev
2025-05-19 18:57 ` |SUCCESS| pw153525 " checkpatch
2025-05-19 20:03 ` 0-day Robot [this message]
2025-05-20 2:29 ` |PENDING| pw153521-153525 [PATCH] [25.11,v2,5/5] eventdev: refactor dpdklab
2025-05-20 2:35 ` |SUCCESS| " dpdklab
2025-05-20 2:36 ` |PENDING| " dpdklab
2025-05-20 2:37 ` |SUCCESS| " dpdklab
2025-05-20 2:43 ` dpdklab
2025-05-20 2:45 ` |PENDING| " dpdklab
2025-05-20 2:46 ` |SUCCESS| " dpdklab
2025-05-20 2:53 ` dpdklab
2025-05-20 2:53 ` dpdklab
2025-05-20 2:54 ` |WARNING| " dpdklab
2025-05-20 2:54 ` |SUCCESS| " dpdklab
2025-05-20 3:02 ` dpdklab
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=20250519200309.44925-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=pbhagavatula@marvell.com \
--cc=test-report@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).