From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] cc4a158e69d7088d7b66eb6fb394a68aa9558b95
Date: Sun, 11 Jan 2026 19:16:01 -0800 (PST) [thread overview]
Message-ID: <69646771.170a0220.28584e.e4acSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: 23.11-staging
cc4a158e69d7088d7b66eb6fb394a68aa9558b95 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#33333
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| Fedora Linux 43 | PASS |
+-------------------------------+----------------+
| Debian GNU/Linux 12 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 10.1 | PASS |
+-------------------------------+----------------+
| Fedora Linux 42 | PASS |
+-------------------------------+----------------+
| Fedora Linux 41 | PASS |
+-------------------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------------+
| CentOS Stream 10 | PASS |
+-------------------------------+----------------+
| CentOS Stream 9 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.7 | PASS |
+-------------------------------+----------------+
| Ubuntu 24.04 | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 | PASS |
+-------------------------------+----------------+
| Windows Server 2022 | FAIL |
+-------------------------------+----------------+
==== Unit test summary for Windows Server 2022 (dpdk_unit_test): ====
Failed to get the unit test results.
Displaying the unit test results is not supported for some environments,
such as our aarch32 testing, where meson is not used to run the tests.
Download the logs available on our CI site.
==== End log output ====
Fedora Linux 43
Kernel: 5.15
Compiler: gcc gcc (GCC) 15.2.1 20251211 (Red Hat 15.2.1-5)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Red Hat Enterprise Linux 10.1
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20250617 (Red Hat 14.3.1-2)
Fedora Linux 42
Kernel: 5.15
Compiler: gcc gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)
Fedora Linux 41
Kernel: 5.15
Compiler: clang gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
CentOS Stream 10
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-14)
Red Hat Enterprise Linux 8.10
Kernel: 5.15
Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-28)
Red Hat Enterprise Linux 9.7
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
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/tarballs/35965/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2026-01-12 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 3:16 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 3:24 dpdklab
2026-01-05 19:26 dpdklab
2026-01-05 16:36 dpdklab
2026-01-05 16:06 dpdklab
2026-01-05 15:56 dpdklab
2026-01-05 15:40 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=69646771.170a0220.28584e.e4acSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--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).