From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andre Muezerie <andremue@linux.microsoft.com>
Subject: |FAILURE| pw153337 [PATCH] [v2,1/1] buildtools: avoid break due to f
Date: Wed, 07 May 2025 10:06:31 -0700 (PDT) [thread overview]
Message-ID: <681b9317.050a0220.241043.fcd7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1746569662-11532-2-git-send-email-andremue@linux.microsoft.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/153337
_Testing issues_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Tuesday, May 06 2025 22:14:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:75f179ebe347b6098cf3af26d3d3b7168fe3fe24
153337 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#28376
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 10 | WARN |
+---------------------+----------------+
| Debian 12 | WARN |
+---------------------+----------------+
| CentOS Stream 9 | WARN |
+---------------------+----------------+
| Fedora 40 | WARN |
+---------------------+----------------+
| Fedora 41 | WARN |
+---------------------+----------------+
| Fedora 40 (Clang) | WARN |
+---------------------+----------------+
| RHEL9 | WARN |
+---------------------+----------------+
| RHEL8 | WARN |
+---------------------+----------------+
| Fedora 41 (Clang) | WARN |
+---------------------+----------------+
| Ubuntu 22.04 | WARN |
+---------------------+----------------+
| Ubuntu 24.04 | WARN |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
| 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 10
Kernel: Depends on container host
Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 41
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Fedora 41 (Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: 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/patchsets/33130/
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:[~2025-05-07 17:06 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1746569662-11532-2-git-send-email-andremue@linux.microsoft.com>
2025-05-06 21:40 ` |FAILURE| pw153337 [PATCH v2 1/1] buildtools: avoid break due to failure to cleanup temporary directory qemudev
2025-05-06 22:15 ` |SUCCESS| " checkpatch
2025-05-06 22:44 ` |FAILURE| " 0-day Robot
2025-05-07 1:32 ` |SUCCESS| pw153337 [PATCH] [v2,1/1] buildtools: avoid break due to f dpdklab
2025-05-07 1:32 ` dpdklab
2025-05-07 1:43 ` dpdklab
2025-05-07 1:43 ` dpdklab
2025-05-07 1:44 ` dpdklab
2025-05-07 1:47 ` dpdklab
2025-05-07 1:59 ` dpdklab
2025-05-07 2:25 ` |WARNING| " dpdklab
2025-05-07 2:45 ` dpdklab
2025-05-07 2:47 ` dpdklab
2025-05-07 2:49 ` dpdklab
2025-05-07 3:00 ` |SUCCESS| " dpdklab
2025-05-07 3:10 ` dpdklab
2025-05-07 3:12 ` dpdklab
2025-05-07 3:14 ` dpdklab
2025-05-07 3:14 ` dpdklab
2025-05-07 3:24 ` dpdklab
2025-05-07 3:26 ` dpdklab
2025-05-07 3:38 ` |WARNING| " dpdklab
2025-05-07 3:39 ` dpdklab
2025-05-07 3:39 ` dpdklab
2025-05-07 3:41 ` |SUCCESS| " dpdklab
2025-05-07 4:02 ` |WARNING| " dpdklab
2025-05-07 4:10 ` |FAILURE| " dpdklab
2025-05-07 4:18 ` dpdklab
2025-05-07 4:19 ` dpdklab
2025-05-07 4:23 ` dpdklab
2025-05-07 4:25 ` dpdklab
2025-05-07 4:28 ` dpdklab
2025-05-07 4:29 ` dpdklab
2025-05-07 4:31 ` dpdklab
2025-05-07 4:32 ` dpdklab
2025-05-07 4:33 ` dpdklab
2025-05-07 4:33 ` dpdklab
2025-05-07 4:36 ` |WARNING| " dpdklab
2025-05-07 4:37 ` dpdklab
2025-05-07 4:37 ` dpdklab
2025-05-07 4:38 ` dpdklab
2025-05-07 4:58 ` |FAILURE| " dpdklab
2025-05-07 5:29 ` dpdklab
2025-05-07 5:30 ` dpdklab
2025-05-07 5:30 ` dpdklab
2025-05-07 5:31 ` dpdklab
2025-05-07 5:33 ` dpdklab
2025-05-07 5:36 ` dpdklab
2025-05-07 5:40 ` dpdklab
2025-05-07 5:41 ` dpdklab
2025-05-07 5:42 ` dpdklab
2025-05-07 5:43 ` dpdklab
2025-05-07 5:44 ` dpdklab
2025-05-07 5:44 ` dpdklab
2025-05-07 5:44 ` dpdklab
2025-05-07 7:05 ` dpdklab
2025-05-07 7:13 ` dpdklab
2025-05-07 16:06 ` dpdklab
2025-05-07 16:10 ` dpdklab
2025-05-07 16:32 ` dpdklab
2025-05-07 16:37 ` dpdklab
2025-05-07 17:01 ` dpdklab
2025-05-07 17:06 ` dpdklab [this message]
2025-05-07 17:48 ` |WARNING| " dpdklab
2025-05-07 18:36 ` 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=681b9317.050a0220.241043.fcd7SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andremue@linux.microsoft.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).