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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 62f583c49bf67dd4d6733ece14e55fe6839e66d1
Date: Thu, 02 Oct 2025 21:18:17 -0700 (PDT)	[thread overview]
Message-ID: <68df4e89.170a0220.369f22.1c28SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v23.11

62f583c49bf67dd4d6733ece14e55fe6839e66d1 --> testing issues

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

Test environment and result as below:

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

==== 20 line log output for Windows Server 2022 (dpdk_llvm_clang_compile): ====
Compiler for C supports arguments -mavx512f: YES (cached)
Compiler for C supports arguments -mavx512bw: YES (cached)
Compiler for C supports arguments -mavx512dq: YES (cached)
Compiler for C supports arguments -march=skylake-avx512: YES
Message: drivers/common/idpf: Defining dependency "common_idpf"
Message: drivers/bus/auxiliary: Defining dependency "bus_auxiliary"
Compiler for C supports arguments -Wno-cast-qual: YES (cached)
Compiler for C supports arguments -Wno-pointer-arith: YES (cached)
Message: drivers/bus/pci: Defining dependency "bus_pci"
Message: drivers/bus/vdev: Defining dependency "bus_vdev"
Compiler for C supports arguments -std=c11: YES
Compiler for C supports arguments -Wno-strict-prototypes: YES
Compiler for C supports arguments -D_BSD_SOURCE: YES
Compiler for C supports arguments -D_DEFAULT_SOURCE: YES
Compiler for C supports arguments -D_XOPEN_SOURCE=600: YES
Has header "mlx5devx.h" : YES

drivers\common\mlx5\windows\meson.build:10:13: ERROR: C shared or static library 'mlx5devx' not found

A full log can be found at C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Native\dpdk\build\meson-logs\meson-log.txt
==== End log output ====

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

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/35090/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2025-10-03  4:18 UTC|newest]

Thread overview: 185+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03  4:18 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-03  5:07 dpdklab
2025-10-03  4:53 dpdklab
2025-10-03  4:40 dpdklab
2025-10-03  2:06 dpdklab
2025-10-03  1:31 dpdklab
2025-10-03  1:31 dpdklab
2025-10-03  1:31 dpdklab
2025-10-02 21:35 dpdklab
2025-10-02 21:35 dpdklab
2025-10-02 13:59 dpdklab
2025-10-02  6:09 dpdklab
2025-10-02  5:05 dpdklab
2025-10-02  4:32 dpdklab
2025-10-02  4:28 dpdklab
2025-10-01 13:11 dpdklab
2025-10-01  6:16 dpdklab
2025-10-01  5:18 dpdklab
2025-10-01  4:44 dpdklab
2025-09-30 16:41 dpdklab
2025-09-30 14:07 dpdklab
2025-09-30 14:07 dpdklab
2025-09-30 12:28 dpdklab
2025-09-30  5:16 dpdklab
2025-09-30  4:34 dpdklab
2025-09-30  4:19 dpdklab
2025-09-30  4:08 dpdklab
2025-09-30  4:07 dpdklab
2025-09-30  4:05 dpdklab
2025-09-30  4:05 dpdklab
2025-09-29  6:08 dpdklab
2025-09-29  6:08 dpdklab
2025-09-29  5:48 dpdklab
2025-09-29  4:52 dpdklab
2025-09-29  4:37 dpdklab
2025-09-29  4:22 dpdklab
2025-09-28  5:12 dpdklab
2025-09-28  5:11 dpdklab
2025-09-28  4:50 dpdklab
2025-09-28  4:06 dpdklab
2025-09-28  4:06 dpdklab
2025-09-28  4:05 dpdklab
2025-09-27  5:55 dpdklab
2025-09-27  5:29 dpdklab
2025-09-27  5:26 dpdklab
2025-09-27  5:24 dpdklab
2025-09-27  4:24 dpdklab
2025-09-27  4:19 dpdklab
2025-09-27  4:17 dpdklab
2025-09-27  4:13 dpdklab
2025-09-26  6:49 dpdklab
2025-09-26  6:35 dpdklab
2025-09-26  6:35 dpdklab
2025-09-26  6:09 dpdklab
2025-09-26  4:32 dpdklab
2025-09-26  4:26 dpdklab
2025-09-26  4:18 dpdklab
2025-09-25 15:42 dpdklab
2025-09-25  6:58 dpdklab
2025-09-25  5:26 dpdklab
2025-09-25  5:26 dpdklab
2025-09-25  5:26 dpdklab
2025-09-25  4:54 dpdklab
2025-09-25  4:08 dpdklab
2025-09-25  4:08 dpdklab
2025-09-24  7:14 dpdklab
2025-09-24  7:04 dpdklab
2025-09-24  6:03 dpdklab
2025-09-24  5:34 dpdklab
2025-09-24  5:23 dpdklab
2025-09-24  4:46 dpdklab
2025-09-24  4:38 dpdklab
2025-09-24  4:19 dpdklab
2025-09-23  7:03 dpdklab
2025-09-23  4:58 dpdklab
2025-09-23  4:58 dpdklab
2025-09-23  4:57 dpdklab
2025-09-23  4:27 dpdklab
2025-09-23  4:07 dpdklab
2025-09-23  4:06 dpdklab
2025-09-22  7:21 dpdklab
2025-09-22  7:16 dpdklab
2025-09-22  5:34 dpdklab
2025-09-22  5:05 dpdklab
2025-09-22  5:02 dpdklab
2025-09-22  4:53 dpdklab
2025-09-22  4:42 dpdklab
2025-09-22  4:20 dpdklab
2025-09-21  6:38 dpdklab
2025-09-21  5:04 dpdklab
2025-09-21  4:50 dpdklab
2025-09-21  4:20 dpdklab
2025-09-21  4:07 dpdklab
2025-09-21  4:06 dpdklab
2025-09-20  7:46 dpdklab
2025-09-20  6:43 dpdklab
2025-09-20  5:15 dpdklab
2025-09-20  5:15 dpdklab
2025-09-20  4:46 dpdklab
2025-09-20  4:08 dpdklab
2025-09-20  4:08 dpdklab
2025-09-20  4:06 dpdklab
2025-09-19  8:19 dpdklab
2025-09-19  5:40 dpdklab
2025-09-19  5:05 dpdklab
2025-09-19  4:34 dpdklab
2025-09-19  4:27 dpdklab
2025-09-19  4:27 dpdklab
2025-09-19  4:18 dpdklab
2025-09-19  4:15 dpdklab
2025-09-18  8:49 dpdklab
2025-09-18  7:42 dpdklab
2025-09-18  5:22 dpdklab
2025-09-18  5:18 dpdklab
2025-09-18  4:41 dpdklab
2025-09-18  4:36 dpdklab
2025-09-18  4:28 dpdklab
2025-09-17 11:29 dpdklab
2025-09-17  8:37 dpdklab
2025-09-17  6:52 dpdklab
2025-09-17  5:39 dpdklab
2025-09-17  5:18 dpdklab
2025-09-17  5:18 dpdklab
2025-09-17  5:14 dpdklab
2025-09-17  5:14 dpdklab
2025-09-16  8:00 dpdklab
2025-09-16  6:04 dpdklab
2025-09-16  5:21 dpdklab
2025-09-16  4:57 dpdklab
2025-09-16  4:11 dpdklab
2025-09-16  4:10 dpdklab
2025-09-16  4:10 dpdklab
2025-09-16  4:09 dpdklab
2025-09-16  4:07 dpdklab
2025-09-15  8:12 dpdklab
2025-09-15  6:05 dpdklab
2025-09-15  5:42 dpdklab
2025-09-15  5:39 dpdklab
2025-09-15  5:22 dpdklab
2025-09-15  4:57 dpdklab
2025-09-15  4:49 dpdklab
2025-09-15  4:25 dpdklab
2025-09-14  6:55 dpdklab
2025-09-14  6:33 dpdklab
2025-09-14  5:15 dpdklab
2025-09-14  5:12 dpdklab
2025-09-14  4:45 dpdklab
2025-09-14  4:44 dpdklab
2025-09-14  4:32 dpdklab
2025-09-14  4:24 dpdklab
2025-09-13 11:00 dpdklab
2025-09-13  8:06 dpdklab
2025-09-13  8:06 dpdklab
2025-09-13  6:36 dpdklab
2025-09-13  6:30 dpdklab
2025-09-13  6:09 dpdklab
2025-09-13  4:41 dpdklab
2025-09-13  4:36 dpdklab
2025-09-13  4:18 dpdklab
2025-09-12 16:53 dpdklab
2025-09-12  8:58 dpdklab
2025-09-12  7:47 dpdklab
2025-09-12  5:33 dpdklab
2025-09-12  5:12 dpdklab
2025-09-12  4:09 dpdklab
2025-09-12  4:09 dpdklab
2025-09-12  4:08 dpdklab
2025-09-11 23:32 dpdklab
2025-09-11 18:44 dpdklab
2025-09-11 11:03 dpdklab
2025-09-11  5:32 dpdklab
2025-09-11  4:35 dpdklab
2025-09-11  4:29 dpdklab
2025-09-11  4:20 dpdklab
2025-09-11  4:15 dpdklab
2025-09-10  7:30 dpdklab
2025-09-10  5:24 dpdklab
2025-09-10  5:12 dpdklab
2025-09-10  4:50 dpdklab
2025-09-10  4:43 dpdklab
2025-09-10  4:43 dpdklab
2025-09-10  4:35 dpdklab
2025-09-10  4:35 dpdklab
2025-09-10  4:35 dpdklab
2025-09-10  4:17 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=68df4e89.170a0220.369f22.1c28SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).