From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 84bfce561f24a33cb186efdc1cf8dc4a8c96fd26
Date: Wed, 03 Jan 2024 15:24:19 -0800 (PST) [thread overview]
Message-ID: <6595eca3.170a0220.c7c95.74f5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
84bfce561f24a33cb186efdc1cf8dc4a8c96fd26 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27539/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-03 23:24 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 23:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 22:36 dpdklab
2024-01-04 22:27 dpdklab
2024-01-04 7:35 dpdklab
2024-01-04 1:14 dpdklab
2024-01-04 1:06 dpdklab
2024-01-04 0:15 dpdklab
2024-01-04 0:08 dpdklab
2024-01-04 0:04 dpdklab
2024-01-03 23:59 dpdklab
2024-01-03 23:37 dpdklab
2024-01-03 23:36 dpdklab
2024-01-03 23:36 dpdklab
2024-01-03 23:19 dpdklab
2024-01-03 23:07 dpdklab
2024-01-03 23:06 dpdklab
2024-01-03 23:05 dpdklab
2024-01-03 23:05 dpdklab
2024-01-03 23:05 dpdklab
2024-01-03 23:03 dpdklab
2024-01-03 23:03 dpdklab
2024-01-03 23:03 dpdklab
2024-01-03 23:02 dpdklab
2024-01-03 23:02 dpdklab
2024-01-03 23:01 dpdklab
2024-01-03 23:01 dpdklab
2024-01-03 23:00 dpdklab
2024-01-03 22:59 dpdklab
2024-01-03 22:58 dpdklab
2024-01-03 22:57 dpdklab
2024-01-03 22:56 dpdklab
2024-01-03 22:56 dpdklab
2024-01-03 22:56 dpdklab
2024-01-03 22:55 dpdklab
2024-01-03 22:55 dpdklab
2024-01-03 22:55 dpdklab
2024-01-03 22:53 dpdklab
2024-01-03 22:52 dpdklab
2024-01-03 22:51 dpdklab
2024-01-03 22:51 dpdklab
2024-01-03 22:50 dpdklab
2024-01-03 22:44 dpdklab
2024-01-03 22:44 dpdklab
2024-01-03 22:42 dpdklab
2024-01-03 22:42 dpdklab
2024-01-03 22:40 dpdklab
2024-01-03 22:39 dpdklab
2024-01-03 22:38 dpdklab
2024-01-03 22:38 dpdklab
2024-01-03 22:36 dpdklab
2024-01-03 22:35 dpdklab
2024-01-03 22:33 dpdklab
2024-01-03 22:32 dpdklab
2024-01-03 22:29 dpdklab
2024-01-03 22:23 dpdklab
2023-12-15 5:36 dpdklab
2023-12-14 23:37 dpdklab
2023-12-14 23:36 dpdklab
2023-12-14 22:11 dpdklab
2023-12-14 21:48 dpdklab
2023-12-14 21:40 dpdklab
2023-12-14 21:31 dpdklab
2023-12-14 21:26 dpdklab
2023-12-14 21:26 dpdklab
2023-12-14 21:26 dpdklab
2023-12-14 21:23 dpdklab
2023-12-14 21:22 dpdklab
2023-12-14 21:20 dpdklab
2023-12-14 21:18 dpdklab
2023-12-14 21:17 dpdklab
2023-12-14 21:16 dpdklab
2023-12-14 21:16 dpdklab
2023-12-14 21:16 dpdklab
2023-12-14 21:12 dpdklab
2023-12-14 21:08 dpdklab
2023-12-14 21:08 dpdklab
2023-12-14 21:07 dpdklab
2023-12-14 21:06 dpdklab
2023-12-14 21:05 dpdklab
2023-12-14 21:01 dpdklab
2023-12-14 20:58 dpdklab
2023-12-14 20:57 dpdklab
2023-12-14 20:42 dpdklab
2023-12-14 20:40 dpdklab
2023-12-14 20:40 dpdklab
2023-12-14 20:37 dpdklab
2023-12-14 20:37 dpdklab
2023-12-14 20:37 dpdklab
2023-12-14 20:33 dpdklab
2023-12-14 20:30 dpdklab
2023-12-14 20:30 dpdklab
2023-12-14 20:28 dpdklab
2023-12-14 20:26 dpdklab
2023-12-14 20:26 dpdklab
2023-12-14 20:26 dpdklab
2023-12-14 20:21 dpdklab
2023-12-14 20:07 dpdklab
2023-12-14 19:59 dpdklab
2023-12-14 19:58 dpdklab
2023-12-14 19:57 dpdklab
2023-12-14 19:57 dpdklab
2023-12-14 19:49 dpdklab
2023-12-14 19:45 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=6595eca3.170a0220.c7c95.74f5SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).