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] 592c7bf7148bec1a34db79370e968dd2d1f8f1dc
Date: Wed, 11 May 2022 01:11:11 -0400 (EDT) [thread overview]
Message-ID: <20220511051111.BC0B2EEACA@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
_Functional Testing PASS_
Branch: tags/v21.11
592c7bf7148bec1a34db79370e968dd2d1f8f1dc --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/19763/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-05-11 5:11 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 5:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-17 9:51 dpdklab
2022-05-17 8:55 dpdklab
2022-05-17 8:51 dpdklab
2022-05-17 8:21 dpdklab
2022-05-17 5:58 dpdklab
2022-05-17 5:43 dpdklab
2022-05-17 5:40 dpdklab
2022-05-17 5:38 dpdklab
2022-05-17 5:26 dpdklab
2022-05-17 4:55 dpdklab
2022-05-16 7:43 dpdklab
2022-05-16 7:18 dpdklab
2022-05-16 7:06 dpdklab
2022-05-16 7:01 dpdklab
2022-05-16 6:55 dpdklab
2022-05-16 5:41 dpdklab
2022-05-16 5:34 dpdklab
2022-05-16 5:29 dpdklab
2022-05-16 5:18 dpdklab
2022-05-16 5:10 dpdklab
2022-05-15 7:18 dpdklab
2022-05-15 7:13 dpdklab
2022-05-15 7:00 dpdklab
2022-05-15 6:51 dpdklab
2022-05-15 6:29 dpdklab
2022-05-15 5:41 dpdklab
2022-05-15 5:33 dpdklab
2022-05-15 5:29 dpdklab
2022-05-15 5:17 dpdklab
2022-05-15 5:09 dpdklab
2022-05-14 7:14 dpdklab
2022-05-14 6:59 dpdklab
2022-05-14 6:58 dpdklab
2022-05-14 6:54 dpdklab
2022-05-14 6:52 dpdklab
2022-05-14 5:41 dpdklab
2022-05-14 5:33 dpdklab
2022-05-14 5:21 dpdklab
2022-05-14 5:17 dpdklab
2022-05-14 5:08 dpdklab
2022-05-13 13:00 dpdklab
2022-05-13 8:53 dpdklab
2022-05-13 8:40 dpdklab
2022-05-13 8:06 dpdklab
2022-05-13 6:46 dpdklab
2022-05-13 5:52 dpdklab
2022-05-13 5:40 dpdklab
2022-05-13 5:39 dpdklab
2022-05-13 5:28 dpdklab
2022-05-13 5:10 dpdklab
2022-05-12 22:32 dpdklab
2022-05-12 18:04 dpdklab
2022-05-12 9:27 dpdklab
2022-05-12 7:41 dpdklab
2022-05-12 7:18 dpdklab
2022-05-12 5:48 dpdklab
2022-05-12 5:40 dpdklab
2022-05-12 5:36 dpdklab
2022-05-12 5:24 dpdklab
2022-05-12 5:15 dpdklab
2022-05-12 5:14 dpdklab
2022-05-11 12:56 dpdklab
2022-05-11 12:17 dpdklab
2022-05-11 9:47 dpdklab
2022-05-11 8:02 dpdklab
2022-05-11 7:57 dpdklab
2022-05-11 7:47 dpdklab
2022-05-11 6:44 dpdklab
2022-05-11 6:12 dpdklab
2022-05-11 5:54 dpdklab
2022-05-11 5:42 dpdklab
2022-05-11 5:34 dpdklab
2022-05-11 5:22 dpdklab
2022-05-11 5:17 dpdklab
2022-05-11 5:08 dpdklab
2022-05-11 4:11 dpdklab
2022-05-11 3:59 dpdklab
2022-05-11 3:47 dpdklab
2022-05-11 3:40 dpdklab
2022-05-11 3:31 dpdklab
2022-05-11 3:14 dpdklab
2022-05-11 3:03 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=20220511051111.BC0B2EEACA@noxus.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).