From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| [GIT MASTER] d32d6c8e31923c3a1eeebe7da6ded89332830576
Date: Fri, 19 Jul 2024 04:41:36 -0700 (PDT) [thread overview]
Message-ID: <669a50f0.050a0220.a86d2.2fa7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing pending_
Branch: dpdk-next-net
d32d6c8e31923c3a1eeebe7da6ded89332830576 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#241754
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 37 | PEND |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 39 | PEND |
+---------------------+----------------+
| Fedora 38 (Clang) | PEND |
+---------------------+----------------+
| Fedora 39 (Clang) | PEND |
+---------------------+----------------+
| Fedora 40 | PEND |
+---------------------+----------------+
| Fedora 40 (Clang) | PEND |
+---------------------+----------------+
| openSUSE Leap 15 | PEND |
+---------------------+----------------+
| RHEL8 | PEND |
+---------------------+----------------+
| RHEL9 | PEND |
+---------------------+----------------+
| Ubuntu 20.04 | PEND |
+---------------------+----------------+
| Ubuntu 22.04 | PEND |
+---------------------+----------------+
| Ubuntu 24.04 | PEND |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.1.1
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29911/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-07-19 11:41 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 11:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-19 13:14 dpdklab
2024-07-19 13:13 dpdklab
2024-07-19 13:09 dpdklab
2024-07-19 13:09 dpdklab
2024-07-19 13:03 dpdklab
2024-07-19 12:49 dpdklab
2024-07-19 12:49 dpdklab
2024-07-19 12:47 dpdklab
2024-07-19 12:46 dpdklab
2024-07-19 12:40 dpdklab
2024-07-19 12:39 dpdklab
2024-07-19 12:38 dpdklab
2024-07-19 12:35 dpdklab
2024-07-19 12:34 dpdklab
2024-07-19 12:33 dpdklab
2024-07-19 12:26 dpdklab
2024-07-19 12:25 dpdklab
2024-07-19 12:20 dpdklab
2024-07-19 12:17 dpdklab
2024-07-19 12:05 dpdklab
2024-07-19 12:01 dpdklab
2024-07-19 12:00 dpdklab
2024-07-19 11:57 dpdklab
2024-07-19 11:57 dpdklab
2024-07-19 11:57 dpdklab
2024-07-19 11:57 dpdklab
2024-07-19 11:56 dpdklab
2024-07-19 11:56 dpdklab
2024-07-19 11:55 dpdklab
2024-07-19 11:54 dpdklab
2024-07-19 11:54 dpdklab
2024-07-19 11:53 dpdklab
2024-07-19 11:53 dpdklab
2024-07-19 11:53 dpdklab
2024-07-19 11:52 dpdklab
2024-07-19 11:52 dpdklab
2024-07-19 11:50 dpdklab
2024-07-19 11:49 dpdklab
2024-07-19 11:48 dpdklab
2024-07-19 11:45 dpdklab
2024-07-19 11:44 dpdklab
2024-07-19 11:43 dpdklab
2024-07-19 11:38 dpdklab
2024-07-19 11:37 dpdklab
2024-07-19 11:36 dpdklab
2024-07-19 11:36 dpdklab
2024-07-19 11:25 dpdklab
2024-07-19 11:24 dpdklab
2024-07-19 11:24 dpdklab
2024-07-19 11:22 dpdklab
2024-07-19 11:17 dpdklab
2024-07-19 11:16 dpdklab
2024-07-19 11:13 dpdklab
2024-07-19 11:09 dpdklab
2024-07-19 11:01 dpdklab
2024-07-19 10:59 dpdklab
2024-07-19 10:57 dpdklab
2024-07-19 10:55 dpdklab
2024-07-19 10:53 dpdklab
2024-07-19 10:52 dpdklab
2024-07-19 10:51 dpdklab
2024-07-19 10:48 dpdklab
2024-07-19 10:48 dpdklab
2024-07-19 10:43 dpdklab
2024-07-19 10:42 dpdklab
2024-07-19 10:42 dpdklab
2024-07-19 10:40 dpdklab
2024-07-19 10:38 dpdklab
2024-07-19 10:38 dpdklab
2024-07-19 10:35 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=669a50f0.050a0220.a86d2.2fa7SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--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).