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] 4e50ad4469f7c037e32de5aa3535d1cd25de0741
Date: Thu, 18 Apr 2024 06:54:20 -0700 (PDT) [thread overview]
Message-ID: <6621260c.050a0220.f3e3e.36efSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: 21.11-staging
4e50ad4469f7c037e32de5aa3535d1cd25de0741 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 39 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian 12 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL 7 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for FreeBSD 13.2 (dpdk_meson_compile): ====
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 14.0.5
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.6
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 39
Kernel: Depends on container host
Compiler: clang 17.0.6
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
RHEL 7
Kernel: 5.4.0-167-generic
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28870/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-04-18 13:54 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 13:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-18 18:33 dpdklab
2024-04-18 16:11 dpdklab
2024-04-18 16:07 dpdklab
2024-04-18 16:04 dpdklab
2024-04-18 15:57 dpdklab
2024-04-18 15:08 dpdklab
2024-04-18 14:57 dpdklab
2024-04-18 14:02 dpdklab
2024-04-18 14:01 dpdklab
2024-04-18 13:59 dpdklab
2024-04-18 13:59 dpdklab
2024-04-18 13:59 dpdklab
2024-04-18 13:57 dpdklab
2024-04-18 13:57 dpdklab
2024-04-18 13:56 dpdklab
2024-04-18 13:55 dpdklab
2024-04-18 13:54 dpdklab
2024-04-18 13:53 dpdklab
2024-04-18 13:53 dpdklab
2024-04-18 13:52 dpdklab
2024-04-18 13:52 dpdklab
2024-04-18 13:51 dpdklab
2024-04-18 13:49 dpdklab
2024-04-18 13:48 dpdklab
2024-04-18 13:47 dpdklab
2024-04-18 13:46 dpdklab
2024-04-18 13:44 dpdklab
2024-04-18 13:43 dpdklab
2024-04-18 13:42 dpdklab
2024-04-18 13:39 dpdklab
2024-04-18 13:39 dpdklab
2024-04-18 13:38 dpdklab
2024-04-18 13:38 dpdklab
2024-04-18 13:26 dpdklab
2024-04-18 13:25 dpdklab
2024-04-18 13:24 dpdklab
2024-04-18 13:24 dpdklab
2024-04-18 13:23 dpdklab
2023-10-18 10:13 dpdklab
2023-10-17 5:14 dpdklab
2023-10-17 5:09 dpdklab
2023-10-16 22:45 dpdklab
2023-10-16 22:32 dpdklab
2023-09-02 5:32 dpdklab
2023-09-02 5:18 dpdklab
2023-09-02 5:09 dpdklab
2023-09-02 5:07 dpdklab
2023-09-02 4:57 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=6621260c.050a0220.f3e3e.36efSMTPIN_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).