From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] fa6a754e746551382922c8be4db0e8f8e39bab40
Date: Sat, 11 Nov 2023 18:22:36 -0800 (PST) [thread overview]
Message-ID: <655036ec.170a0220.5e609.697aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
fa6a754e746551382922c8be4db0e8f8e39bab40 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Arch Linux | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
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
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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)
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
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26950/
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-12 2:22 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 2:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 2:59 dpdklab
2023-11-15 2:39 dpdklab
2023-11-14 21:17 dpdklab
2023-11-14 20:58 dpdklab
2023-11-12 5:03 dpdklab
2023-11-12 2:38 dpdklab
2023-11-12 2:34 dpdklab
2023-11-12 2:31 dpdklab
2023-11-12 2:29 dpdklab
2023-11-12 2:28 dpdklab
2023-11-12 2:25 dpdklab
2023-11-12 2:25 dpdklab
2023-11-12 2:24 dpdklab
2023-11-12 2:23 dpdklab
2023-11-12 2:23 dpdklab
2023-11-12 2:23 dpdklab
2023-11-12 2:23 dpdklab
2023-11-12 2:23 dpdklab
2023-11-12 2:23 dpdklab
2023-11-12 2:23 dpdklab
2023-11-12 2:22 dpdklab
2023-11-12 2:22 dpdklab
2023-11-12 2:22 dpdklab
2023-11-12 2:21 dpdklab
2023-11-12 2:21 dpdklab
2023-11-12 2:21 dpdklab
2023-11-12 2:21 dpdklab
2023-11-12 2:21 dpdklab
2023-11-12 2:21 dpdklab
2023-11-12 2:20 dpdklab
2023-11-12 2:20 dpdklab
2023-11-12 2:20 dpdklab
2023-11-12 2:19 dpdklab
2023-11-12 2:19 dpdklab
2023-11-12 2:19 dpdklab
2023-11-12 2:19 dpdklab
2023-11-12 2:18 dpdklab
2023-11-12 2:18 dpdklab
2023-11-12 2:18 dpdklab
2023-11-12 2:18 dpdklab
2023-11-12 2:17 dpdklab
2023-11-12 2:17 dpdklab
2023-11-12 2:17 dpdklab
2023-11-12 2:16 dpdklab
2023-11-12 2:16 dpdklab
2023-11-12 2:16 dpdklab
2023-11-12 2:15 dpdklab
2023-11-12 2:15 dpdklab
2023-11-12 2:14 dpdklab
2023-11-12 2:13 dpdklab
2023-11-12 2:13 dpdklab
2023-11-12 2:12 dpdklab
2023-11-12 2:12 dpdklab
2023-11-12 2:11 dpdklab
2023-11-11 3:37 dpdklab
2023-11-11 2:50 dpdklab
2023-11-11 2:29 dpdklab
2023-11-11 2:29 dpdklab
2023-11-11 2:25 dpdklab
2023-11-11 2:24 dpdklab
2023-11-11 2:22 dpdklab
2023-11-11 2:21 dpdklab
2023-11-11 2:21 dpdklab
2023-11-11 2:21 dpdklab
2023-11-11 2:21 dpdklab
2023-11-11 2:21 dpdklab
2023-11-11 2:20 dpdklab
2023-11-11 2:20 dpdklab
2023-11-11 2:19 dpdklab
2023-11-11 2:19 dpdklab
2023-11-11 2:17 dpdklab
2023-11-11 2:16 dpdklab
2023-11-11 2:16 dpdklab
2023-11-11 2:16 dpdklab
2023-11-11 2:16 dpdklab
2023-11-11 2:16 dpdklab
2023-11-11 2:16 dpdklab
2023-11-11 2:15 dpdklab
2023-11-11 2:15 dpdklab
2023-11-11 2:15 dpdklab
2023-11-11 2:14 dpdklab
2023-11-11 2:13 dpdklab
2023-11-11 2:13 dpdklab
2023-11-11 2:13 dpdklab
2023-11-11 2:13 dpdklab
2023-11-11 2:12 dpdklab
2023-11-11 2:12 dpdklab
2023-11-11 2:12 dpdklab
2023-11-11 2:12 dpdklab
2023-11-11 2:12 dpdklab
2023-11-11 2:11 dpdklab
2023-11-11 2:11 dpdklab
2023-11-11 2:11 dpdklab
2023-11-11 2:11 dpdklab
2023-11-11 2:10 dpdklab
2023-11-11 2:10 dpdklab
2023-11-11 2:10 dpdklab
2023-11-11 2:10 dpdklab
2023-11-11 2:10 dpdklab
2023-11-11 2:09 dpdklab
2023-11-11 2:09 dpdklab
2023-11-11 2:09 dpdklab
2023-11-11 2:09 dpdklab
2023-11-11 2:08 dpdklab
2023-11-11 2:08 dpdklab
2023-11-11 2:07 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=655036ec.170a0220.5e609.697aSMTPIN_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).