From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: tduszynski@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw154459 [PATCH 6/6] trace: add PMU
Date: Mon, 16 Jun 2025 03:45:06 -0400 [thread overview]
Message-ID: <20250616074506.2565936-1-robot@bytheb.org> (raw)
In-Reply-To: <20250616065341.3233106-7-tduszynski@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/154459/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15674139018
Build Logs:
-----------------------Summary of failed steps-----------------------
"windows-2022-msvc" failed at step Build
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
"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] "windows-2022-msvc" at step Build
####################################################################################
[79/453] Generating lib/rte_eal_map with a custom command
[80/453] Generating lib/rte_ring_map with a custom command
[81/453] Compiling C object lib/librte_ring.a.p/ring_rte_ring.c.obj
[82/453] Compiling C object lib/librte_ring.a.p/ring_rte_soring.c.obj
[83/453] Compiling C object lib/librte_eal.a.p/eal_x86_rte_mmu.c.obj
[84/453] Generating lib/rte_rcu_map with a custom command
[85/453] Linking static target lib/librte_eal.a
[86/453] Compiling C object lib/librte_ring.a.p/ring_soring.c.obj
[87/453] Compiling C object lib/librte_mempool.a.p/mempool_rte_mempool_ops.c.obj
[88/453] Linking target lib/rte_eal-25.dll
FAILED: lib/rte_eal-25.dll
"link" /MACHINE:x64 /OUT:lib/rte_eal-25.dll lib/librte_eal.a.p/eal_common_eal_common_bus.c.obj lib/librte_eal.a.p/eal_common_eal_common_class.c.obj lib/librte_eal.a.p/eal_common_eal_common_config.c.obj lib/librte_eal.a.p/eal_common_eal_common_debug.c.obj lib/librte_eal.a.p/eal_common_eal_common_dev.c.obj lib/librte_eal.a.p/eal_common_eal_common_devargs.c.obj lib/librte_eal.a.p/eal_common_eal_common_errno.c.obj lib/librte_eal.a.p/eal_common_eal_common_fbarray.c.obj lib/librte_eal.a.p/eal_common_eal_common_hexdump.c.obj lib/librte_eal.a.p/eal_common_eal_common_interrupts.c.obj lib/librte_eal.a.p/eal_common_eal_common_launch.c.obj lib/librte_eal.a.p/eal_common_eal_common_lcore.c.obj lib/librte_eal.a.p/eal_common_eal_common_lcore_var.c.obj lib/librte_eal.a.p/eal_common_eal_common_mcfg.c.obj lib/librte_eal.a.p/eal_common_eal_common_memalloc.c.obj lib/librte_eal.a.p/eal_common_eal_common_memory.c.obj lib/librte_eal.a.p/eal_common_eal_common_memzone.c.obj lib/librte_eal.a.p/eal_common_eal_common_options.c.obj lib/librte_eal.a.p/eal_common_eal_common_string_fns.c.obj lib/librte_eal.a.p/eal_common_eal_common_tailqs.c.obj lib/librte_eal.a.p/eal_common_eal_common_thread.c.obj lib/librte_eal.a.p/eal_common_eal_common_timer.c.obj lib/librte_eal.a.p/eal_common_eal_common_trace_pmu.c.obj lib/librte_eal.a.p/eal_common_eal_common_trace_points.c.obj lib/librte_eal.a.p/eal_common_eal_common_uuid.c.obj lib/librte_eal.a.p/eal_common_malloc_elem.c.obj lib/librte_eal.a.p/eal_common_malloc_heap.c.obj lib/librte_eal.a.p/eal_common_rte_bitset.c.obj lib/librte_eal.a.p/eal_common_rte_malloc.c.obj lib/librte_eal.a.p/eal_common_rte_random.c.obj lib/librte_eal.a.p/eal_common_rte_reciprocal.c.obj lib/librte_eal.a.p/eal_common_rte_service.c.obj lib/librte_eal.a.p/eal_common_rte_version.c.obj lib/librte_eal.a.p/eal_common_eal_common_dynmem.c.obj lib/librte_eal.a.p/eal_windows_eal.c.obj lib/librte_eal.a.p/eal_windows_eal_alarm.c.obj lib/librte_eal.a.p/eal_windows_eal_debug.c.obj lib/librte_eal.a.p/eal_windows_eal_dev.c.obj lib/librte_eal.a.p/eal_windows_eal_file.c.obj lib/librte_eal.a.p/eal_windows_eal_hugepages.c.obj lib/librte_eal.a.p/eal_windows_eal_interrupts.c.obj lib/librte_eal.a.p/eal_windows_eal_lcore.c.obj lib/librte_eal.a.p/eal_windows_eal_memalloc.c.obj lib/librte_eal.a.p/eal_windows_eal_memory.c.obj lib/librte_eal.a.p/eal_windows_eal_mp.c.obj lib/librte_eal.a.p/eal_windows_eal_thread.c.obj lib/librte_eal.a.p/eal_windows_eal_timer.c.obj lib/librte_eal.a.p/eal_windows_getline.c.obj lib/librte_eal.a.p/eal_windows_getopt.c.obj lib/librte_eal.a.p/eal_windows_rte_thread.c.obj lib/librte_eal.a.p/eal_x86_rte_cpuflags.c.obj lib/librte_eal.a.p/eal_x86_rte_cycles.c.obj lib/librte_eal.a.p/eal_x86_rte_hypervisor.c.obj lib/librte_eal.a.p/eal_x86_rte_mmu.c.obj lib/librte_eal.a.p/eal_x86_rte_spinlock.c.obj lib/librte_eal.a.p/eal_x86_rte_power_intrinsics.c.obj "/release" "/nologo" "/OPT:REF" "/DLL" "/IMPLIB:lib\rte_eal.lib" "lib/rte_log.lib" "lib/rte_kvargs.lib" "/def:D:\a\dpdk\dpdk\build\lib\eal_exports.map" "dbghelp.lib" "setupapi.lib" "ws2_32.lib" "mincore.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "comdlg32.lib" "advapi32.lib"
eal_exports.map : error LNK2001: unresolved external symbol __rte_pmu_trace_read
lib\rte_eal.lib : fatal error LNK1120: 1 unresolved externals
[89/453] Compiling C object lib/librte_mempool.a.p/mempool_rte_mempool.c.obj
[90/453] Linking static target lib/librte_ring.a
[91/453] Compiling C object lib/librte_mempool.a.p/mempool_rte_mempool_ops_default.c.obj
[92/453] Compiling C object lib/librte_mempool.a.p/mempool_mempool_trace_points.c.obj
[93/453] Compiling C object lib/librte_rcu.a.p/rcu_rte_rcu_qsbr.c.obj
ninja: build stopped: subcommand failed.
INFO: autodetecting backend as ninja
INFO: calculating backend command to run: C:\hostedtoolcache\windows\Python\3.13.4\x64\Scripts\ninja.EXE -C D:/a/dpdk/dpdk/build
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "windows-2022-msvc" at step Build
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
104/106 DPDK:fast-tests / vdev_autotest OK 0.34s
105/106 DPDK:fast-tests / version_autotest OK 0.34s
106/106 DPDK:fast-tests / telemetry_all OK 1.10s
Ok: 99
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 6
Timeout: 0
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-06-16-AM-07-42-54/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-06-16-AM-07-42-54
+ continue
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
119/121 DPDK:fast-tests / vdev_autotest OK 0.24s
120/121 DPDK:fast-tests / version_autotest OK 0.23s
121/121 DPDK:fast-tests / telemetry_all OK 1.06s
Ok: 114
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 6
Timeout: 0
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-06-16-AM-07-26-25/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-06-16-AM-07-26-25
+ continue
+ [ true != true ]
##[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-06-16 7:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250616065341.3233106-7-tduszynski@marvell.com>
2025-06-16 6:21 ` |SUCCESS| pw154454-154459 " qemudev
2025-06-16 6:25 ` qemudev
2025-06-16 6:54 ` |WARNING| pw154459 " checkpatch
2025-06-16 7:45 ` 0-day Robot [this message]
2025-06-16 8:55 ` |SUCCESS| pw154454-154459 [PATCH] [6/6] " dpdklab
2025-06-16 8:56 ` dpdklab
2025-06-16 9:13 ` dpdklab
2025-06-16 9:18 ` dpdklab
2025-06-16 9:24 ` dpdklab
2025-06-16 9:59 ` |PENDING| " dpdklab
2025-06-16 9:59 ` |SUCCESS| " dpdklab
2025-06-16 10:06 ` |FAILURE| " dpdklab
2025-06-16 10:14 ` dpdklab
2025-06-16 10:17 ` dpdklab
2025-06-16 11:04 ` dpdklab
2025-06-16 11:11 ` dpdklab
2025-06-16 11:19 ` |SUCCESS| " dpdklab
2025-06-16 11:19 ` dpdklab
2025-06-16 11:20 ` dpdklab
2025-06-16 11:39 ` |PENDING| " dpdklab
2025-06-16 12:42 ` |FAILURE| " dpdklab
2025-06-16 14:43 ` dpdklab
2025-06-16 15:40 ` |SUCCESS| " 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=20250616074506.2565936-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=tduszynski@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).