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] e4ca3c9295bf08d5b1582766546387af45bd5a08
Date: Mon, 14 Mar 2022 06:51:54 +0000 (UTC) [thread overview]
Message-ID: <20220314065154.3A9F7601B6@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
_Testing PASS_
Branch: tags/v20.11
e4ca3c9295bf08d5b1582766546387af45bd5a08 --> testing pass
Test environment and result as below:
+-------------------------------+----------------+--------------+
| Environment | dpdk_unit_test | lpm_autotest |
+===============================+================+==============+
| Ubuntu 20.04 ARM GCC Native | PASS | SKIPPED |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM Clang Native | PASS | SKIPPED |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | 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 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/19141/
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-14 6:51 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 6:51 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 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:46 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=20220314065154.3A9F7601B6@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).