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] c66daa12e76d7b4912cfb7109a761856a7a873ab
Date: Mon, 23 Dec 2024 23:54:48 -0800 (PST) [thread overview]
Message-ID: <676a68c8.170a0220.55cc.2046SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: tags/v23.11
c66daa12e76d7b4912cfb7109a761856a7a873ab --> testing issues
Upstream job id: Generic-Unit-Test-DPDK#301741
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Fedora 39 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 39 (Clang) | PASS |
+---------------------+----------------+
| Fedora 40 | PASS |
+---------------------+----------------+
| Fedora 41 | PASS |
+---------------------+----------------+
| Fedora 40 (Clang) | PASS |
+---------------------+----------------+
| RHEL9 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Fedora 41 (Clang) | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PEND |
+---------------------+----------------+
| Ubuntu 20.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 ====
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)
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.6 (Fedora 18.1.6-3.fc40)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
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 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.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/32037/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-24 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 7:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-24 8:04 dpdklab
2024-12-24 8:00 dpdklab
2024-12-24 7:50 dpdklab
2024-12-24 7:49 dpdklab
2024-12-24 7:46 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=676a68c8.170a0220.55cc.2046SMTPIN_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).