From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Bing Zhao <bingz@nvidia.com>
Subject: |FAILURE| pw159584 [PATCH] net/mlx5: fix MPESW PF probe
Date: Fri, 09 Jan 2026 05:03:56 -0800 (PST) [thread overview]
Message-ID: <6960fcbc.170a0220.34838f.c520SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260105132941.72705-1-bingz@nvidia.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/159584
_Testing issues_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, January 05 2026 13:29:41
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:1b8a03f181d93c751ebea9df1584628f485ec745
159584 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#33304
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| CentOS Stream 9 | PASS |
+-------------------------------+----------------+
| CentOS Stream 10 | PASS |
+-------------------------------+----------------+
| Debian GNU/Linux 12 | PASS |
+-------------------------------+----------------+
| Fedora Linux 40 | PASS |
+-------------------------------+----------------+
| Fedora Linux 41 | PASS |
+-------------------------------+----------------+
| Fedora Linux 42 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PASS |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.7 | PASS |
+-------------------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 | PASS |
+-------------------------------+----------------+
| Ubuntu 24.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 ====
CentOS Stream 9
Kernel: 5.15
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-14)
CentOS Stream 10
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20251022 (Red Hat 14.3.1-4)
Debian GNU/Linux 12
Kernel: 5.15
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 40
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 41
Kernel: 5.15
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Fedora Linux 42
Kernel: 5.15
Compiler: clang gcc (GCC) 15.2.1 20251111 (Red Hat 15.2.1-4)
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 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 24.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.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/patchsets/34809/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2026-01-09 13:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260105132941.72705-1-bingz@nvidia.com>
2026-01-05 13:01 ` |SUCCESS| " qemudev
2026-01-05 13:06 ` qemudev
2026-01-05 13:31 ` checkpatch
2026-01-05 14:24 ` 0-day Robot
2026-01-05 14:24 ` 0-day Robot
2026-01-08 1:26 ` dpdklab
2026-01-08 1:37 ` dpdklab
2026-01-08 6:58 ` |PENDING| " dpdklab
2026-01-08 21:13 ` |SUCCESS| " dpdklab
2026-01-08 21:13 ` dpdklab
2026-01-08 21:14 ` dpdklab
2026-01-08 21:15 ` dpdklab
2026-01-08 21:17 ` dpdklab
2026-01-08 21:17 ` dpdklab
2026-01-08 21:18 ` dpdklab
2026-01-08 21:25 ` dpdklab
2026-01-08 22:25 ` dpdklab
2026-01-08 22:40 ` dpdklab
2026-01-08 23:45 ` dpdklab
2026-01-08 23:45 ` dpdklab
2026-01-08 23:47 ` dpdklab
2026-01-09 13:03 ` dpdklab [this message]
2026-01-09 19:31 ` dpdklab
2026-01-10 2:17 ` dpdklab
2026-01-10 2:34 ` 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=6960fcbc.170a0220.34838f.c520SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bingz@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).