automatic DPDK test reports
 help / color / mirror / Atom feed
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] 820ca9fccac850557967172cd1ffce2359fa08c2
Date: Wed, 23 Nov 2022 00:48:55 -0500 (EST)	[thread overview]
Message-ID: <20221123054855.7A5F810618C@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

_Functional Testing PASS_

Branch: tags/v20.11

820ca9fccac850557967172cd1ffce2359fa08c2 --> 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/22406/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2022-11-23  5:48 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  5:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-28 10:54 dpdklab
2022-11-28  7:50 dpdklab
2022-11-28  6:28 dpdklab
2022-11-28  6:07 dpdklab
2022-11-28  6:03 dpdklab
2022-11-28  5:57 dpdklab
2022-11-28  5:53 dpdklab
2022-11-28  5:52 dpdklab
2022-11-28  5:49 dpdklab
2022-11-28  5:48 dpdklab
2022-11-27 10:02 dpdklab
2022-11-27  7:04 dpdklab
2022-11-27  6:23 dpdklab
2022-11-27  6:07 dpdklab
2022-11-27  6:04 dpdklab
2022-11-27  5:57 dpdklab
2022-11-27  5:54 dpdklab
2022-11-27  5:53 dpdklab
2022-11-27  5:51 dpdklab
2022-11-27  5:48 dpdklab
2022-11-26 10:07 dpdklab
2022-11-26  7:06 dpdklab
2022-11-26  6:33 dpdklab
2022-11-26  6:09 dpdklab
2022-11-26  6:04 dpdklab
2022-11-26  5:59 dpdklab
2022-11-26  5:53 dpdklab
2022-11-26  5:50 dpdklab
2022-11-26  5:50 dpdklab
2022-11-26  5:50 dpdklab
2022-11-26  5:49 dpdklab
2022-11-25 10:07 dpdklab
2022-11-25  7:45 dpdklab
2022-11-25  6:23 dpdklab
2022-11-25  6:08 dpdklab
2022-11-25  6:04 dpdklab
2022-11-25  5:58 dpdklab
2022-11-25  5:54 dpdklab
2022-11-25  5:53 dpdklab
2022-11-25  5:49 dpdklab
2022-11-25  5:48 dpdklab
2022-11-24  9:55 dpdklab
2022-11-24  8:15 dpdklab
2022-11-24  6:28 dpdklab
2022-11-24  6:09 dpdklab
2022-11-24  6:06 dpdklab
2022-11-24  5:59 dpdklab
2022-11-24  5:58 dpdklab
2022-11-24  5:53 dpdklab
2022-11-24  5:50 dpdklab
2022-11-24  5:50 dpdklab
2022-11-24  5:49 dpdklab
2022-11-23 10:09 dpdklab
2022-11-23  7:53 dpdklab
2022-11-23  6:24 dpdklab
2022-11-23  6:10 dpdklab
2022-11-23  6:04 dpdklab
2022-11-23  6:00 dpdklab
2022-11-23  5:53 dpdklab
2022-11-23  5:53 dpdklab
2022-11-23  5:50 dpdklab
2022-11-23  5:50 dpdklab
2022-11-22 10:23 dpdklab
2022-11-22  8:24 dpdklab
2022-11-22  6:31 dpdklab
2022-11-22  6:10 dpdklab
2022-11-22  6:04 dpdklab
2022-11-22  6:00 dpdklab
2022-11-22  5:54 dpdklab
2022-11-22  5:53 dpdklab
2022-11-22  5:50 dpdklab
2022-11-22  5:50 dpdklab
2022-11-22  5:50 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=20221123054855.7A5F810618C@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).