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] 6ae8ba6b7aec5fbbce3449abe0c13c40d21561b9
Date: Sat, 19 Mar 2022 06:04:54 +0000 (UTC) [thread overview]
Message-ID: <20220319060454.81FAD601C4@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
_Testing PASS_
Branch: tags/v21.11
6ae8ba6b7aec5fbbce3449abe0c13c40d21561b9 --> testing pass
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM GCC Native | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Native | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/19190/
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-19 6:04 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 6:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-21 5:34 dpdklab
2022-03-21 5:31 dpdklab
2022-03-21 5:28 dpdklab
2022-03-21 5:24 dpdklab
2022-03-21 5:24 dpdklab
2022-03-21 5:23 dpdklab
2022-03-21 5:17 dpdklab
2022-03-21 5:08 dpdklab
2022-03-21 5:07 dpdklab
2022-03-20 5:39 dpdklab
2022-03-20 5:37 dpdklab
2022-03-20 5:32 dpdklab
2022-03-20 5:31 dpdklab
2022-03-20 5:25 dpdklab
2022-03-20 5:09 dpdklab
2022-03-20 5:08 dpdklab
2022-03-20 5:08 dpdklab
2022-03-19 6:12 dpdklab
2022-03-19 6:05 dpdklab
2022-03-19 5:33 dpdklab
2022-03-19 5:13 dpdklab
2022-03-19 5:12 dpdklab
2022-03-19 5:08 dpdklab
2022-03-19 5:07 dpdklab
2022-03-18 7:16 dpdklab
2022-03-18 6:29 dpdklab
2022-03-18 6:19 dpdklab
2022-03-18 5:32 dpdklab
2022-03-18 5:24 dpdklab
2022-03-18 5:17 dpdklab
2022-03-18 5:12 dpdklab
2022-03-18 5:11 dpdklab
2022-03-18 5:08 dpdklab
2022-03-17 10:03 dpdklab
2022-03-17 9:10 dpdklab
2022-03-17 7:58 dpdklab
2022-03-17 7:03 dpdklab
2022-03-17 5:33 dpdklab
2022-03-17 5:26 dpdklab
2022-03-17 5:24 dpdklab
2022-03-17 5:10 dpdklab
2022-03-17 5:10 dpdklab
2022-03-17 5:08 dpdklab
2022-03-17 5:07 dpdklab
2022-03-17 4:15 dpdklab
2022-03-17 4:08 dpdklab
2022-03-17 3:32 dpdklab
2022-03-17 3:15 dpdklab
2022-03-17 3:11 dpdklab
2022-03-17 3:08 dpdklab
2022-03-17 3:02 dpdklab
2022-03-17 3:02 dpdklab
2022-03-17 2:56 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=20220319060454.81FAD601C4@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).