From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
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] 40f28803d54dc91940a9c7332345c5fc1a3f4e71
Date: Sun, 27 Feb 2022 00:50:27 -0500 (EST) [thread overview]
Message-ID: <20220227055027.188E26D4C2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
_Functional Testing PASS_
Branch: tags/v20.11
40f28803d54dc91940a9c7332345c5fc1a3f4e71 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/18925/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-02-27 5:50 UTC|newest]
Thread overview: 159+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 5:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-07 10:25 dpdklab
2022-03-07 7:58 dpdklab
2022-03-07 6:27 dpdklab
2022-03-07 6:15 dpdklab
2022-03-07 6:09 dpdklab
2022-03-07 6:05 dpdklab
2022-03-07 6:00 dpdklab
2022-03-07 5:54 dpdklab
2022-03-07 5:52 dpdklab
2022-03-07 5:51 dpdklab
2022-03-07 5:49 dpdklab
2022-03-07 5:48 dpdklab
2022-03-06 19:03 dpdklab
2022-03-06 16:08 dpdklab
2022-03-06 9:50 dpdklab
2022-03-06 7:25 dpdklab
2022-03-06 6:41 dpdklab
2022-03-06 6:10 dpdklab
2022-03-06 6:06 dpdklab
2022-03-06 6:02 dpdklab
2022-03-06 5:59 dpdklab
2022-03-06 5:56 dpdklab
2022-03-06 5:54 dpdklab
2022-03-06 5:52 dpdklab
2022-03-06 5:50 dpdklab
2022-03-06 4:31 dpdklab
2022-03-05 21:37 dpdklab
2022-03-05 16:31 dpdklab
2022-03-05 6:41 dpdklab
2022-03-05 6:41 dpdklab
2022-03-05 6:39 dpdklab
2022-03-05 6:10 dpdklab
2022-03-05 6:05 dpdklab
2022-03-05 6:01 dpdklab
2022-03-05 5:56 dpdklab
2022-03-05 5:53 dpdklab
2022-03-05 5:51 dpdklab
2022-03-05 5:49 dpdklab
2022-03-05 5:49 dpdklab
2022-03-04 21:10 dpdklab
2022-03-04 20:23 dpdklab
2022-03-04 17:07 dpdklab
2022-03-04 7:34 dpdklab
2022-03-04 6:10 dpdklab
2022-03-04 6:06 dpdklab
2022-03-04 6:01 dpdklab
2022-03-04 5:56 dpdklab
2022-03-04 5:53 dpdklab
2022-03-04 5:52 dpdklab
2022-03-04 5:50 dpdklab
2022-03-04 5:50 dpdklab
2022-03-04 4:40 dpdklab
2022-03-03 17:16 dpdklab
2022-03-03 8:59 dpdklab
2022-03-03 6:12 dpdklab
2022-03-03 6:07 dpdklab
2022-03-03 6:01 dpdklab
2022-03-03 6:00 dpdklab
2022-03-03 5:55 dpdklab
2022-03-03 5:53 dpdklab
2022-03-03 5:50 dpdklab
2022-03-03 5:50 dpdklab
2022-03-03 4:26 dpdklab
2022-03-02 19:58 dpdklab
2022-03-02 8:52 dpdklab
2022-03-02 8:35 dpdklab
2022-03-02 7:36 dpdklab
2022-03-02 6:36 dpdklab
2022-03-02 6:06 dpdklab
2022-03-02 5:59 dpdklab
2022-03-02 5:55 dpdklab
2022-03-02 5:54 dpdklab
2022-03-02 5:53 dpdklab
2022-03-02 5:52 dpdklab
2022-03-02 5:49 dpdklab
2022-03-02 5:49 dpdklab
2022-03-02 5:49 dpdklab
2022-03-01 16:17 dpdklab
2022-03-01 10:48 dpdklab
2022-03-01 8:04 dpdklab
2022-03-01 6:47 dpdklab
2022-03-01 6:10 dpdklab
2022-03-01 6:05 dpdklab
2022-03-01 6:00 dpdklab
2022-03-01 5:58 dpdklab
2022-03-01 5:54 dpdklab
2022-03-01 5:54 dpdklab
2022-03-01 5:52 dpdklab
2022-03-01 5:49 dpdklab
2022-03-01 5:48 dpdklab
2022-02-28 17:58 dpdklab
2022-02-28 13:06 dpdklab
2022-02-28 12:10 dpdklab
2022-02-28 10:09 dpdklab
2022-02-28 8:15 dpdklab
2022-02-28 6:12 dpdklab
2022-02-28 6:08 dpdklab
2022-02-28 6:01 dpdklab
2022-02-28 6:01 dpdklab
2022-02-28 5:55 dpdklab
2022-02-28 5:54 dpdklab
2022-02-28 5:50 dpdklab
2022-02-28 5:47 dpdklab
2022-02-28 5:47 dpdklab
2022-02-27 12:18 dpdklab
2022-02-27 10:06 dpdklab
2022-02-27 8:08 dpdklab
2022-02-27 6:58 dpdklab
2022-02-27 6:05 dpdklab
2022-02-27 6:02 dpdklab
2022-02-27 6:00 dpdklab
2022-02-27 5:57 dpdklab
2022-02-27 5:55 dpdklab
2022-02-27 5:49 dpdklab
2022-02-27 5:48 dpdklab
2022-02-27 5:47 dpdklab
2022-02-27 5:35 dpdklab
2022-02-26 11:26 dpdklab
2022-02-26 9:06 dpdklab
2022-02-26 7:45 dpdklab
2022-02-26 6:09 dpdklab
2022-02-26 6:04 dpdklab
2022-02-26 6:01 dpdklab
2022-02-26 6:00 dpdklab
2022-02-26 5:59 dpdklab
2022-02-26 5:58 dpdklab
2022-02-26 5:55 dpdklab
2022-02-26 5:50 dpdklab
2022-02-26 5:48 dpdklab
2022-02-26 5:46 dpdklab
2022-02-25 22:17 dpdklab
2022-02-25 10:37 dpdklab
2022-02-25 8:10 dpdklab
2022-02-25 8:03 dpdklab
2022-02-25 7:14 dpdklab
2022-02-25 6:21 dpdklab
2022-02-25 6:15 dpdklab
2022-02-25 6:12 dpdklab
2022-02-25 6:12 dpdklab
2022-02-25 6:07 dpdklab
2022-02-25 6:06 dpdklab
2022-02-25 6:01 dpdklab
2022-02-25 6:01 dpdklab
2022-02-25 6:01 dpdklab
2022-02-25 4:44 dpdklab
2022-02-24 11:08 dpdklab
2022-02-24 9:40 dpdklab
2022-02-24 9:05 dpdklab
2022-02-24 7:29 dpdklab
2022-02-24 6:13 dpdklab
2022-02-24 6:05 dpdklab
2022-02-24 6:02 dpdklab
2022-02-24 6:01 dpdklab
2022-02-24 6:00 dpdklab
2022-02-24 5:56 dpdklab
2022-02-24 5:52 dpdklab
2022-02-24 5:52 dpdklab
2022-02-24 5:48 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=20220227055027.188E26D4C2@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--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).