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] bb5ce0625c6b43d5d3ac16258515274721c192e7
Date: Fri, 1 Apr 2022 01:09:23 -0400 (EDT) [thread overview]
Message-ID: <20220401050923.4D1AA6D45F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
_Functional Testing PASS_
Branch: tags/v21.11
bb5ce0625c6b43d5d3ac16258515274721c192e7 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
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/19316/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-04-01 5:09 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 5:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-01 7:20 dpdklab
2022-04-01 6:39 dpdklab
2022-04-01 6:38 dpdklab
2022-04-01 6:38 dpdklab
2022-04-01 5:32 dpdklab
2022-04-01 5:25 dpdklab
2022-04-01 5:24 dpdklab
2022-04-01 5:07 dpdklab
2022-04-01 5:07 dpdklab
2022-03-31 7:41 dpdklab
2022-03-31 7:16 dpdklab
2022-03-31 7:02 dpdklab
2022-03-31 6:58 dpdklab
2022-03-31 6:02 dpdklab
2022-03-31 5:55 dpdklab
2022-03-31 5:50 dpdklab
2022-03-31 5:43 dpdklab
2022-03-31 5:38 dpdklab
2022-03-31 5:35 dpdklab
2022-03-31 5:27 dpdklab
2022-03-31 5:24 dpdklab
2022-03-31 5:18 dpdklab
2022-03-31 5:15 dpdklab
2022-03-31 5:11 dpdklab
2022-03-31 5:10 dpdklab
2022-03-30 9:41 dpdklab
2022-03-30 8:44 dpdklab
2022-03-30 8:18 dpdklab
2022-03-30 6:10 dpdklab
2022-03-30 5:54 dpdklab
2022-03-30 5:47 dpdklab
2022-03-30 5:35 dpdklab
2022-03-30 5:17 dpdklab
2022-03-30 5:07 dpdklab
2022-03-30 4:56 dpdklab
2022-03-29 9:51 dpdklab
2022-03-29 9:11 dpdklab
2022-03-29 9:10 dpdklab
2022-03-29 7:26 dpdklab
2022-03-29 5:31 dpdklab
2022-03-29 5:24 dpdklab
2022-03-29 5:12 dpdklab
2022-03-29 5:08 dpdklab
2022-03-29 5:08 dpdklab
2022-03-29 4:55 dpdklab
2022-03-28 7:56 dpdklab
2022-03-28 7:01 dpdklab
2022-03-28 6:52 dpdklab
2022-03-28 6:52 dpdklab
2022-03-28 5:31 dpdklab
2022-03-28 5:24 dpdklab
2022-03-28 5:23 dpdklab
2022-03-28 5:16 dpdklab
2022-03-28 5:09 dpdklab
2022-03-28 5:07 dpdklab
2022-03-27 7:19 dpdklab
2022-03-27 6:38 dpdklab
2022-03-27 6:37 dpdklab
2022-03-27 6:34 dpdklab
2022-03-27 5:33 dpdklab
2022-03-27 5:26 dpdklab
2022-03-27 5:24 dpdklab
2022-03-27 5:09 dpdklab
2022-03-27 5:08 dpdklab
2022-03-27 5:08 dpdklab
2022-03-26 9:03 dpdklab
2022-03-26 8:06 dpdklab
2022-03-26 7:30 dpdklab
2022-03-26 6:39 dpdklab
2022-03-26 5:33 dpdklab
2022-03-26 5:25 dpdklab
2022-03-26 5:13 dpdklab
2022-03-26 5:13 dpdklab
2022-03-26 5:10 dpdklab
2022-03-26 5:08 dpdklab
2022-03-26 5:08 dpdklab
2022-03-26 4:19 dpdklab
2022-03-26 4:07 dpdklab
2022-03-26 3:17 dpdklab
2022-03-26 3:16 dpdklab
2022-03-26 3:11 dpdklab
2022-03-26 3:02 dpdklab
2022-03-26 2:57 dpdklab
2022-03-26 2:56 dpdklab
2022-03-26 2:55 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=20220401050923.4D1AA6D45F@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).