From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] e4ca3c9295bf08d5b1582766546387af45bd5a08
Date: Fri, 11 Mar 2022 06:46:55 +0000 (UTC) [thread overview]
Message-ID: <20220311064655.5F441601B6@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3644 bytes --]
_Testing PASS_
Branch: tags/v20.11
e4ca3c9295bf08d5b1582766546387af45bd5a08 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| CentOS 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 31 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 18.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL 7 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 clang | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 32 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 33 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Arch Linux | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0 and gcc 8.1.0 (MinGW)
CentOS 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
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
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
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 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/19123/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-03-11 6:46 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 6:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-24 4:22 dpdklab
2022-03-24 4:14 dpdklab
2022-03-24 1:43 dpdklab
2022-03-24 1:32 dpdklab
2022-03-24 1:04 dpdklab
2022-03-24 0:53 dpdklab
2022-03-23 22:27 dpdklab
2022-03-23 22:16 dpdklab
2022-03-15 9:16 dpdklab
2022-03-15 8:01 dpdklab
2022-03-15 5:54 dpdklab
2022-03-15 5:04 dpdklab
2022-03-15 5:00 dpdklab
2022-03-15 4:57 dpdklab
2022-03-15 4:55 dpdklab
2022-03-15 4:49 dpdklab
2022-03-15 4:47 dpdklab
2022-03-14 6:52 dpdklab
2022-03-14 6:51 dpdklab
2022-03-14 5:52 dpdklab
2022-03-14 5:05 dpdklab
2022-03-14 5:01 dpdklab
2022-03-14 4:59 dpdklab
2022-03-14 4:56 dpdklab
2022-03-14 4:54 dpdklab
2022-03-14 4:50 dpdklab
2022-03-13 6:40 dpdklab
2022-03-13 6:39 dpdklab
2022-03-13 6:35 dpdklab
2022-03-13 6:04 dpdklab
2022-03-13 6:00 dpdklab
2022-03-13 5:57 dpdklab
2022-03-13 5:53 dpdklab
2022-03-13 5:48 dpdklab
2022-03-13 5:46 dpdklab
2022-03-12 10:20 dpdklab
2022-03-12 8:48 dpdklab
2022-03-12 6:52 dpdklab
2022-03-12 6:05 dpdklab
2022-03-12 6:02 dpdklab
2022-03-12 5:59 dpdklab
2022-03-12 5:54 dpdklab
2022-03-12 5:49 dpdklab
2022-03-12 5:47 dpdklab
2022-03-11 10:21 dpdklab
2022-03-11 8:24 dpdklab
2022-03-11 7:43 dpdklab
2022-03-11 6:06 dpdklab
2022-03-11 6:01 dpdklab
2022-03-11 5:59 dpdklab
2022-03-11 5:57 dpdklab
2022-03-11 5:55 dpdklab
2022-03-11 5:50 dpdklab
2022-03-10 7:53 dpdklab
2022-03-10 7:28 dpdklab
2022-03-10 7:22 dpdklab
2022-03-10 6:01 dpdklab
2022-03-10 5:51 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=20220311064655.5F441601B6@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).