From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>
Subject: |FAILURE| pw152266-152267 [PATCH] [RFC,v2,2/2] build: generate symbo
Date: Thu, 06 Mar 2025 06:03:29 -0800 (PST) [thread overview]
Message-ID: <67c9ab31.170a0220.37dc91.1f86SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250306125021.2231121-2-david.marchand@redhat.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/152267
_Testing issues_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Thursday, March 06 2025 12:50:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:47461173800f029033d7088b7d49860ea27305db
152266-152267 --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#322248
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 10 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Fedora 40 | PASS |
+---------------------+----------------+
| Fedora 41 | PEND |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 40 (Clang) | PASS |
+---------------------+----------------+
| RHEL9 | PASS |
+---------------------+----------------+
| Fedora 41 (Clang) | PEND |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Ubuntu 24.04 | PEND |
+---------------------+----------------+
| 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 ====
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
CentOS Stream 10
Kernel: Depends on container host
Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
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)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
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)
Fedora 41 (Clang)
Kernel: Depends on container host
Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
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
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/32765/
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-03-06 14:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250306125021.2231121-2-david.marchand@redhat.com>
2025-03-06 12:20 ` |SUCCESS| pw152266-152267 [RFC v2 2/2] build: generate symbol maps qemudev
2025-03-06 12:25 ` qemudev
2025-03-06 13:17 ` |SUCCESS| pw152266-152267 [PATCH] [RFC,v2,2/2] build: generate symbo dpdklab
2025-03-06 13:24 ` dpdklab
2025-03-06 13:27 ` dpdklab
2025-03-06 13:30 ` |PENDING| " dpdklab
2025-03-06 13:34 ` |FAILURE| " dpdklab
2025-03-06 13:34 ` |PENDING| " dpdklab
2025-03-06 13:35 ` |FAILURE| " dpdklab
2025-03-06 13:36 ` |SUCCESS| " dpdklab
2025-03-06 13:39 ` dpdklab
2025-03-06 13:41 ` |FAILURE| " dpdklab
2025-03-06 13:41 ` |PENDING| " dpdklab
2025-03-06 13:42 ` dpdklab
2025-03-06 13:45 ` |FAILURE| " dpdklab
2025-03-06 13:48 ` |SUCCESS| " dpdklab
2025-03-06 13:50 ` dpdklab
2025-03-06 13:50 ` |FAILURE| " dpdklab
2025-03-06 13:53 ` dpdklab
2025-03-06 13:54 ` |SUCCESS| " dpdklab
2025-03-06 14:02 ` |FAILURE| " dpdklab
2025-03-06 14:03 ` dpdklab [this message]
2025-03-06 14:03 ` dpdklab
2025-03-06 14:03 ` dpdklab
2025-03-06 14:05 ` |SUCCESS| " dpdklab
2025-03-06 14:06 ` |FAILURE| pw152267 [RFC v2 2/2] build: generate symbol maps 0-day Robot
2025-03-06 14:08 ` |FAILURE| pw152266-152267 [PATCH] [RFC,v2,2/2] build: generate symbo dpdklab
2025-03-06 14:20 ` dpdklab
2025-03-06 14:33 ` |SUCCESS| " dpdklab
2025-03-06 14:37 ` |FAILURE| " dpdklab
2025-03-06 15:09 ` |SUCCESS| " dpdklab
2025-03-06 15:47 ` dpdklab
2025-03-06 16:20 ` 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=67c9ab31.170a0220.37dc91.1f86SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.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).