From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@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] f95b184d1e8b9a5f899cfdf3ee389e111289e315
Date: Thu, 7 Jul 2022 06:23:04 +0000 (UTC) [thread overview]
Message-ID: <20220707062304.B36F9600AF@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2630 bytes --]
_Testing PASS_
Branch: tags/v21.11
f95b184d1e8b9a5f899cfdf3ee389e111289e315 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Ubuntu 18.04 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 31 | PASS |
+---------------------+----------------+
| RHEL 7 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Fedora 34 | PASS |
+---------------------+----------------+
| Fedora 32 | PASS |
+---------------------+----------------+
| Fedora 33 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Arch Linux | PASS |
+---------------------+----------------+
| Fedora 34 clang | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
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)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/20670/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-07-07 6:23 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 6:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-12 6:50 dpdklab
2022-07-12 6:40 dpdklab
2022-07-12 6:26 dpdklab
2022-07-12 6:22 dpdklab
2022-07-12 5:47 dpdklab
2022-07-12 5:39 dpdklab
2022-07-12 5:35 dpdklab
2022-07-12 5:22 dpdklab
2022-07-12 5:17 dpdklab
2022-07-12 5:11 dpdklab
2022-07-11 6:28 dpdklab
2022-07-11 6:17 dpdklab
2022-07-11 6:02 dpdklab
2022-07-11 5:56 dpdklab
2022-07-11 5:45 dpdklab
2022-07-11 5:43 dpdklab
2022-07-11 5:37 dpdklab
2022-07-11 5:24 dpdklab
2022-07-11 5:24 dpdklab
2022-07-11 5:24 dpdklab
2022-07-10 6:56 dpdklab
2022-07-10 6:33 dpdklab
2022-07-10 6:25 dpdklab
2022-07-10 6:23 dpdklab
2022-07-10 6:12 dpdklab
2022-07-10 5:43 dpdklab
2022-07-10 5:35 dpdklab
2022-07-10 5:31 dpdklab
2022-07-10 5:24 dpdklab
2022-07-10 5:16 dpdklab
2022-07-09 7:06 dpdklab
2022-07-09 6:55 dpdklab
2022-07-09 6:46 dpdklab
2022-07-09 6:33 dpdklab
2022-07-09 6:27 dpdklab
2022-07-09 5:44 dpdklab
2022-07-09 5:34 dpdklab
2022-07-09 5:33 dpdklab
2022-07-09 5:23 dpdklab
2022-07-09 5:05 dpdklab
2022-07-08 8:00 dpdklab
2022-07-08 7:17 dpdklab
2022-07-08 6:34 dpdklab
2022-07-08 6:30 dpdklab
2022-07-08 6:03 dpdklab
2022-07-08 5:46 dpdklab
2022-07-08 5:38 dpdklab
2022-07-08 5:34 dpdklab
2022-07-08 5:24 dpdklab
2022-07-08 5:14 dpdklab
2022-07-07 7:27 dpdklab
2022-07-07 6:55 dpdklab
2022-07-07 6:18 dpdklab
2022-07-07 6:08 dpdklab
2022-07-07 5:45 dpdklab
2022-07-07 5:42 dpdklab
2022-07-07 5:33 dpdklab
2022-07-07 5:26 dpdklab
2022-07-07 5:25 dpdklab
2022-07-06 6:36 dpdklab
2022-07-06 6:18 dpdklab
2022-07-06 6:17 dpdklab
2022-07-06 6:10 dpdklab
2022-07-06 6:09 dpdklab
2022-07-06 5:44 dpdklab
2022-07-06 5:35 dpdklab
2022-07-06 5:33 dpdklab
2022-07-06 5:23 dpdklab
2022-07-06 5:13 dpdklab
2022-07-05 6:57 dpdklab
2022-07-05 6:35 dpdklab
2022-07-05 6:30 dpdklab
2022-07-05 6:17 dpdklab
2022-07-05 6:16 dpdklab
2022-07-05 5:42 dpdklab
2022-07-05 5:34 dpdklab
2022-07-05 5:29 dpdklab
2022-07-05 5:18 dpdklab
2022-07-05 5:11 dpdklab
2022-07-04 14:46 dpdklab
2022-07-04 12:22 dpdklab
2022-07-04 7:09 dpdklab
2022-07-04 6:51 dpdklab
2022-07-04 6:26 dpdklab
2022-07-04 6:24 dpdklab
2022-07-04 6:05 dpdklab
2022-07-04 5:55 dpdklab
2022-07-04 5:50 dpdklab
2022-07-04 5:46 dpdklab
2022-07-04 5:38 dpdklab
2022-07-04 5:34 dpdklab
2022-07-04 5:26 dpdklab
2022-07-03 6:40 dpdklab
2022-07-03 6:33 dpdklab
2022-07-03 6:23 dpdklab
2022-07-03 6:14 dpdklab
2022-07-03 5:43 dpdklab
2022-07-03 5:35 dpdklab
2022-07-03 5:31 dpdklab
2022-07-03 5:23 dpdklab
2022-07-03 5:11 dpdklab
2022-07-02 6:39 dpdklab
2022-07-02 6:37 dpdklab
2022-07-02 6:33 dpdklab
2022-07-02 6:33 dpdklab
2022-07-02 5:47 dpdklab
2022-07-02 5:39 dpdklab
2022-07-02 5:28 dpdklab
2022-07-02 5:27 dpdklab
2022-07-02 5:23 dpdklab
2022-07-02 4:26 dpdklab
2022-07-02 4:08 dpdklab
2022-07-02 3:39 dpdklab
2022-07-02 3:38 dpdklab
2022-07-02 3:24 dpdklab
2022-07-02 3:20 dpdklab
2022-07-02 3:11 dpdklab
2022-07-02 3:05 dpdklab
2022-07-02 3:05 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=20220707062304.B36F9600AF@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--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).