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] 170c1249980a64615caba36b192a813e1a9f46af
Date: Wed, 23 Mar 2022 22:04:57 -0400 (EDT) [thread overview]
Message-ID: <20220324020457.49478104A1@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
_Functional Testing PASS_
Branch: tags/v21.11
170c1249980a64615caba36b192a813e1a9f46af --> 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/19134/
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-24 2:04 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 2:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-24 4:43 dpdklab
2022-03-24 4:30 dpdklab
2022-03-24 1:55 dpdklab
2022-03-24 1:24 dpdklab
2022-03-24 1:15 dpdklab
2022-03-23 22:47 dpdklab
2022-03-23 22:36 dpdklab
2022-03-23 22:08 dpdklab
2022-03-23 21:56 dpdklab
2022-03-16 7:15 dpdklab
2022-03-16 7:14 dpdklab
2022-03-16 7:12 dpdklab
2022-03-16 7:03 dpdklab
2022-03-16 5:31 dpdklab
2022-03-16 5:24 dpdklab
2022-03-16 5:24 dpdklab
2022-03-16 5:07 dpdklab
2022-03-16 5:07 dpdklab
2022-03-16 4:57 dpdklab
2022-03-15 7:24 dpdklab
2022-03-15 7:17 dpdklab
2022-03-15 7:13 dpdklab
2022-03-15 7:00 dpdklab
2022-03-15 5:31 dpdklab
2022-03-15 5:24 dpdklab
2022-03-15 5:23 dpdklab
2022-03-15 5:08 dpdklab
2022-03-15 5:08 dpdklab
2022-03-15 5:07 dpdklab
2022-03-14 8:05 dpdklab
2022-03-14 7:21 dpdklab
2022-03-14 7:07 dpdklab
2022-03-14 7:07 dpdklab
2022-03-14 5:32 dpdklab
2022-03-14 5:25 dpdklab
2022-03-14 5:24 dpdklab
2022-03-14 5:18 dpdklab
2022-03-14 5:09 dpdklab
2022-03-14 5:07 dpdklab
2022-03-13 7:47 dpdklab
2022-03-13 7:46 dpdklab
2022-03-13 7:28 dpdklab
2022-03-13 7:23 dpdklab
2022-03-13 6:31 dpdklab
2022-03-13 6:24 dpdklab
2022-03-13 6:23 dpdklab
2022-03-13 6:16 dpdklab
2022-03-13 6:10 dpdklab
2022-03-13 6:07 dpdklab
2022-03-12 9:06 dpdklab
2022-03-12 8:26 dpdklab
2022-03-12 8:14 dpdklab
2022-03-12 8:03 dpdklab
2022-03-12 6:32 dpdklab
2022-03-12 6:25 dpdklab
2022-03-12 6:24 dpdklab
2022-03-12 6:08 dpdklab
2022-03-12 6:08 dpdklab
2022-03-12 6:02 dpdklab
2022-03-11 8:47 dpdklab
2022-03-11 7:58 dpdklab
2022-03-11 7:58 dpdklab
2022-03-11 7:44 dpdklab
2022-03-11 6:33 dpdklab
2022-03-11 6:25 dpdklab
2022-03-11 6:13 dpdklab
2022-03-11 6:10 dpdklab
2022-03-11 6:09 dpdklab
2022-03-11 6:09 dpdklab
2022-03-11 6:08 dpdklab
2022-03-11 5:54 dpdklab
2022-03-11 5:46 dpdklab
2022-03-11 5:26 dpdklab
2022-03-11 4:20 dpdklab
2022-03-11 4:14 dpdklab
2022-03-11 4:07 dpdklab
2022-03-11 4:05 dpdklab
2022-03-11 4:04 dpdklab
2022-03-11 4:00 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=20220324020457.49478104A1@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).