From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 502b07c4e0c2b250a33325d6f2fbd28d2aad5af7
Date: Thu, 30 May 2024 04:33:11 -0700 (PDT) [thread overview]
Message-ID: <665863f7.050a0220.ec314.a0dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
502b07c4e0c2b250a33325d6f2fbd28d2aad5af7 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_compile_ovs |
+=====================+====================+======================+==================+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| Windows Server 2022 | PASS | PASS | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| FreeBSD 14.0 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| CentOS Stream 8 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| Debian Bullseye | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| Debian 12 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| CentOS Stream 9 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| Fedora 37 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| openSUSE Leap 15 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| RHEL8 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| Ubuntu 24.04 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| Fedora 38 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
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
FreeBSD 14.0
Kernel: 14.0
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
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
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)
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29252/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-05-30 11:33 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 11:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-30 19:18 dpdklab
2024-05-30 19:14 dpdklab
2024-05-30 19:14 dpdklab
2024-05-30 14:35 dpdklab
2024-05-30 12:43 dpdklab
2024-05-30 12:09 dpdklab
2024-05-30 12:02 dpdklab
2024-05-30 12:01 dpdklab
2024-05-30 11:57 dpdklab
2024-05-30 11:52 dpdklab
2024-05-30 11:46 dpdklab
2024-05-30 11:44 dpdklab
2024-05-30 11:42 dpdklab
2024-05-30 11:41 dpdklab
2024-05-30 11:39 dpdklab
2024-05-30 11:38 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:35 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:34 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:33 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:32 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:31 dpdklab
2024-05-30 11:30 dpdklab
2024-05-30 11:30 dpdklab
2024-05-30 11:30 dpdklab
2024-05-30 11:29 dpdklab
2024-05-30 11:29 dpdklab
2024-05-30 11:29 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:28 dpdklab
2024-05-30 11:27 dpdklab
2024-05-30 11:27 dpdklab
2024-05-30 11:26 dpdklab
2024-05-30 11:26 dpdklab
2024-05-30 11:26 dpdklab
2024-05-30 11:26 dpdklab
2024-05-30 11:25 dpdklab
2024-05-30 11:25 dpdklab
2024-05-30 11:24 dpdklab
2024-05-30 11:24 dpdklab
2024-05-30 11:24 dpdklab
2024-05-30 11:24 dpdklab
2024-05-30 11:23 dpdklab
2024-05-30 11:23 dpdklab
2024-05-30 11:23 dpdklab
2024-05-30 11:23 dpdklab
2024-05-30 11:21 dpdklab
2024-05-30 11:21 dpdklab
2024-05-30 11:21 dpdklab
2024-05-30 11:21 dpdklab
2024-05-30 11:20 dpdklab
2024-05-30 11:20 dpdklab
2024-05-30 11:20 dpdklab
2024-05-30 11:19 dpdklab
2024-05-30 11:19 dpdklab
2024-05-30 11:18 dpdklab
2024-05-30 11:17 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=665863f7.050a0220.ec314.a0dfSMTPIN_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).