From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] 9136514c99c0b1ae9bc0d3c386d2756711b5e9ae
Date: Tue, 28 Nov 2023 16:53:29 -0800 (PST) [thread overview]
Message-ID: <65668b89.170a0220.f91e5.0656SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
9136514c99c0b1ae9bc0d3c386d2756711b5e9ae --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.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
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27150/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-29 0:53 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 0:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-29 3:28 dpdklab
2023-11-29 1:45 dpdklab
2023-11-29 1:26 dpdklab
2023-11-29 1:23 dpdklab
2023-11-29 0:55 dpdklab
2023-11-29 0:54 dpdklab
2023-11-29 0:54 dpdklab
2023-11-29 0:54 dpdklab
2023-11-29 0:52 dpdklab
2023-11-29 0:51 dpdklab
2023-11-29 0:51 dpdklab
2023-11-29 0:50 dpdklab
2023-11-29 0:49 dpdklab
2023-11-29 0:48 dpdklab
2023-11-29 0:46 dpdklab
2023-11-29 0:46 dpdklab
2023-11-29 0:46 dpdklab
2023-11-29 0:45 dpdklab
2023-11-29 0:45 dpdklab
2023-11-29 0:44 dpdklab
2023-11-29 0:44 dpdklab
2023-11-29 0:43 dpdklab
2023-11-29 0:43 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:42 dpdklab
2023-11-29 0:41 dpdklab
2023-11-29 0:41 dpdklab
2023-11-29 0:41 dpdklab
2023-11-29 0:41 dpdklab
2023-11-29 0:41 dpdklab
2023-11-29 0:41 dpdklab
2023-11-29 0:40 dpdklab
2023-11-29 0:40 dpdklab
2023-11-29 0:40 dpdklab
2023-11-29 0:39 dpdklab
2023-11-29 0:38 dpdklab
2023-11-29 0:38 dpdklab
2023-11-29 0:37 dpdklab
2023-11-29 0:37 dpdklab
2023-11-29 0:36 dpdklab
2023-11-29 0:36 dpdklab
2023-11-29 0:36 dpdklab
2023-11-29 0:35 dpdklab
2023-11-29 0:35 dpdklab
2023-11-29 0:34 dpdklab
2023-11-29 0:34 dpdklab
2023-11-29 0:33 dpdklab
2023-11-29 0:33 dpdklab
2023-11-29 0:32 dpdklab
2023-11-28 14:05 dpdklab
2023-11-28 13:28 dpdklab
2023-11-28 12:55 dpdklab
2023-11-28 12:55 dpdklab
2023-11-28 12:52 dpdklab
2023-11-28 12:51 dpdklab
2023-11-28 12:50 dpdklab
2023-11-28 12:48 dpdklab
2023-11-28 12:45 dpdklab
2023-11-28 12:44 dpdklab
2023-11-28 12:42 dpdklab
2023-11-28 12:39 dpdklab
2023-11-28 12:38 dpdklab
2023-11-28 12:38 dpdklab
2023-11-28 12:36 dpdklab
2023-11-28 12:35 dpdklab
2023-11-28 12:35 dpdklab
2023-11-28 12:34 dpdklab
2023-11-28 12:33 dpdklab
2023-11-28 12:33 dpdklab
2023-11-28 12:33 dpdklab
2023-11-28 12:32 dpdklab
2023-11-28 12:32 dpdklab
2023-11-28 12:29 dpdklab
2023-11-28 12:28 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:27 dpdklab
2023-11-28 12:26 dpdklab
2023-11-28 12:25 dpdklab
2023-11-28 12:25 dpdklab
2023-11-28 12:25 dpdklab
2023-11-28 12:25 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:24 dpdklab
2023-11-28 12:23 dpdklab
2023-11-28 12:22 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=65668b89.170a0220.f91e5.0656SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=qi.z.zhang@intel.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).