automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Thomas Monjalon <thomas@monjalon.net>
Subject: |FAILURE| pw154231 [PATCH] [v18] trace: add PMU
Date: Mon, 09 Jun 2025 15:37:42 -0700 (PDT)	[thread overview]
Message-ID: <68476236.050a0220.2c1067.4039SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250609165736.2255515-1-thomas@monjalon.net>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/154231

_Testing issues_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Monday, June 09 2025 16:55:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:98bfa438ca7f80baf155636364377be72b4c75dc

154231 --> testing issues

Upstream job id: Windows-Compile-DPDK-Native#28923

Test environment and result as below:

+---------------------+--------------------+-------------------+-------------------------+
|     Environment     | dpdk_meson_compile | dpdk_msvc_compile | dpdk_llvm_clang_compile |
+=====================+====================+===================+=========================+
| Ubuntu 20.04        | FAIL               | SKIPPED           | SKIPPED                 |
+---------------------+--------------------+-------------------+-------------------------+
| FreeBSD 14.2        | FAIL               | SKIPPED           | SKIPPED                 |
+---------------------+--------------------+-------------------+-------------------------+
| Windows Server 2022 | SKIPPED            | FAIL              | FAIL                    |
+---------------------+--------------------+-------------------+-------------------------+

==== 20 line log output for Windows Server 2022 (dpdk_llvm_clang_compile): ====
..\lib\eal\include\rte_eal_trace.h:131:10: fatal error: 'rte_pmu.h' file not found
#include <rte_pmu.h>
^~~~~~~~~~~
1 error generated.
[327/867] Compiling C object lib/librte_eal.a.p/eal_common_rte_reciprocal.c.obj
[328/867] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_memory.c.obj
[329/867] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_timer.c.obj
[330/867] Compiling C object lib/librte_eal.a.p/eal_common_rte_bitset.c.obj
[331/867] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_trace_pmu.c.obj
FAILED: lib/librte_eal.a.p/eal_common_eal_common_trace_pmu.c.obj
"clang" "-Ilib\librte_eal.a.p" "-Ilib" "-I..\lib" "-Ilib\eal\common" "-I..\lib\eal\common" "-I." "-I.." "-Iconfig" "-I..\config" "-Ilib\eal\include" "-I..\lib\eal\include" "-Ilib\eal\windows\include" "-I..\lib\eal\windows\include" "-Ilib\eal\x86\include" "-I..\lib\eal\x86\include" "-Ilib\eal" "-I..\lib\eal" "-Ilib\log" "-I..\lib\log" "-Ilib\kvargs" "-I..\lib\kvargs" "-IC:\Program Files\Mellanox\MLNX_WinOF2_DevX_SDK\inc" "-Xclang" "-fcolor-diagnostics" "-pipe" "-D_FILE_OFFSET_BITS=64" "-Wall" "-Winvalid-pch" "-Wextra" "-Werror" "-std=c11" "-O3" "-include" "rte_config.h" "-Wvla" "-Wcast-qual" "-Wdeprecated" "-Wformat" "-Wformat-nonliteral" "-Wformat-security" "-Wmissing-declarations" "-Wmissing-prototypes" "-Wnested-externs" "-Wold-style-definition" "-Wpointer-arith" "-Wsign-compare" "-Wstrict-prototypes" "-Wundef" "-Wwrite-strings" "-Wno-missing-field-initializers" "-D_GNU_SOURCE" "-D_WIN32_WINNT=0x0A00" "-D_CRT_SECURE_NO_WARNINGS" "-march=native" "-mrtm" "-DALLOW_EXPERIMENTAL_API" "-
 DALLOW_INTERNAL_API" "-DABI_VERSION=\"25.2\"" "-DRTE_LOG_DEFAULT_LOGTYPE=lib.eal" "-DRTE_ANNOTATE_LOCKS" "-Wthread-safety" -MD -MQ lib/librte_eal.a.p/eal_common_eal_common_trace_pmu.c.obj -MF "lib\librte_eal.a.p\eal_common_eal_common_trace_pmu.c.obj.d" -o lib/librte_eal.a.p/eal_common_eal_common_trace_pmu.c.obj "-c" ../lib/eal/common/eal_common_trace_pmu.c
../lib/eal/common/eal_common_trace_pmu.c:6:10: fatal error: 'rte_pmu.h' file not found
#include <rte_pmu.h>
^~~~~~~~~~~
1 error generated.
[332/867] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_thread.c.obj
[333/867] Compiling C object lib/librte_eal.a.p/eal_windows_eal.c.obj
[334/867] Compiling C object lib/librte_eal.a.p/eal_common_rte_service.c.obj
[335/867] Compiling C object lib/librte_eal.a.p/eal_common_rte_malloc.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 20.04
	Kernel: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33364/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-06-09 22:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250609165736.2255515-1-thomas@monjalon.net>
2025-06-09 16:23 ` |SUCCESS| pw154231 [PATCH v18] " qemudev
2025-06-09 16:28 ` |FAILURE| " qemudev
2025-06-09 16:57 ` |SUCCESS| " checkpatch
2025-06-09 17:24 ` |FAILURE| " 0-day Robot
2025-06-09 22:04 ` |FAILURE| pw154231 [PATCH] [v18] " dpdklab
2025-06-09 22:05 ` dpdklab
2025-06-09 22:10 ` |SUCCESS| " dpdklab
2025-06-09 22:12 ` dpdklab
2025-06-09 22:18 ` |FAILURE| " dpdklab
2025-06-09 22:34 ` |PENDING| " dpdklab
2025-06-09 22:37 ` dpdklab [this message]
2025-06-09 22:40 ` |FAILURE| " dpdklab
2025-06-09 23:04 ` |SUCCESS| " dpdklab
2025-06-09 23:48 ` |FAILURE| " dpdklab
2025-06-10  0:19 ` |WARNING| " dpdklab
2025-06-10  0:20 ` |FAILURE| " dpdklab
2025-06-10  0:21 ` dpdklab
2025-06-10  0:22 ` dpdklab
2025-06-10  0:23 ` dpdklab
2025-06-10  0:51 ` |WARNING| " dpdklab
2025-06-10  3:02 ` |FAILURE| " dpdklab
2025-06-10  3:12 ` dpdklab
2025-06-10  3:16 ` dpdklab
2025-06-10  3:26 ` dpdklab
2025-06-10  4:52 ` dpdklab
2025-06-10  4:53 ` dpdklab
2025-06-10  4:53 ` dpdklab
2025-06-10  4:53 ` 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=68476236.050a0220.2c1067.4039SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).