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] 0c553ce5276d0e2a3576823b8f392db331219151
Date: Mon, 19 Dec 2022 00:56:28 -0500 (EST)	[thread overview]
Message-ID: <20221219055628.1AA104AF@noxus.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing PASS_

Branch: tags/v21.11

0c553ce5276d0e2a3576823b8f392db331219151 --> 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/22665/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-12-19  5:56 UTC|newest]

Thread overview: 129+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  5:56 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-19  7:56 dpdklab
2022-12-19  7:15 dpdklab
2022-12-19  7:13 dpdklab
2022-12-19  7:13 dpdklab
2022-12-19  6:39 dpdklab
2022-12-19  6:20 dpdklab
2022-12-19  6:16 dpdklab
2022-12-19  6:04 dpdklab
2022-12-19  6:01 dpdklab
2022-12-19  6:00 dpdklab
2022-12-18  7:27 dpdklab
2022-12-18  7:02 dpdklab
2022-12-18  6:57 dpdklab
2022-12-18  6:51 dpdklab
2022-12-18  6:45 dpdklab
2022-12-18  6:41 dpdklab
2022-12-18  6:38 dpdklab
2022-12-18  6:19 dpdklab
2022-12-18  6:16 dpdklab
2022-12-18  6:00 dpdklab
2022-12-18  6:00 dpdklab
2022-12-18  5:59 dpdklab
2022-12-18  5:55 dpdklab
2022-12-17  7:32 dpdklab
2022-12-17  7:03 dpdklab
2022-12-17  7:02 dpdklab
2022-12-17  7:01 dpdklab
2022-12-17  7:00 dpdklab
2022-12-17  6:58 dpdklab
2022-12-17  6:56 dpdklab
2022-12-17  6:55 dpdklab
2022-12-17  6:53 dpdklab
2022-12-17  6:48 dpdklab
2022-12-17  6:47 dpdklab
2022-12-17  6:40 dpdklab
2022-12-17  6:38 dpdklab
2022-12-17  6:20 dpdklab
2022-12-17  6:16 dpdklab
2022-12-17  6:04 dpdklab
2022-12-17  6:02 dpdklab
2022-12-17  6:00 dpdklab
2022-12-17  5:55 dpdklab
2022-12-16  7:31 dpdklab
2022-12-16  7:08 dpdklab
2022-12-16  7:07 dpdklab
2022-12-16  7:06 dpdklab
2022-12-16  7:03 dpdklab
2022-12-16  7:02 dpdklab
2022-12-16  6:55 dpdklab
2022-12-16  6:53 dpdklab
2022-12-16  6:52 dpdklab
2022-12-16  6:50 dpdklab
2022-12-16  6:45 dpdklab
2022-12-16  6:43 dpdklab
2022-12-16  6:36 dpdklab
2022-12-16  6:36 dpdklab
2022-12-16  6:18 dpdklab
2022-12-16  6:05 dpdklab
2022-12-16  6:02 dpdklab
2022-12-16  5:55 dpdklab
2022-12-15 10:09 dpdklab
2022-12-15  9:17 dpdklab
2022-12-15  8:14 dpdklab
2022-12-15  8:14 dpdklab
2022-12-15  8:14 dpdklab
2022-12-15  8:13 dpdklab
2022-12-15  7:02 dpdklab
2022-12-15  6:28 dpdklab
2022-12-15  6:17 dpdklab
2022-12-15  6:15 dpdklab
2022-12-15  6:09 dpdklab
2022-12-15  6:05 dpdklab
2022-12-15  6:00 dpdklab
2022-12-15  5:55 dpdklab
2022-12-14  7:38 dpdklab
2022-12-14  7:38 dpdklab
2022-12-14  7:37 dpdklab
2022-12-14  7:36 dpdklab
2022-12-14  7:36 dpdklab
2022-12-14  7:36 dpdklab
2022-12-14  7:35 dpdklab
2022-12-14  7:35 dpdklab
2022-12-14  7:33 dpdklab
2022-12-14  7:20 dpdklab
2022-12-14  7:10 dpdklab
2022-12-14  6:48 dpdklab
2022-12-14  6:20 dpdklab
2022-12-14  6:16 dpdklab
2022-12-14  6:01 dpdklab
2022-12-14  6:00 dpdklab
2022-12-14  5:59 dpdklab
2022-12-14  5:58 dpdklab
2022-12-14  5:55 dpdklab
2022-12-13 10:23 dpdklab
2022-12-13  9:45 dpdklab
2022-12-13  9:45 dpdklab
2022-12-13  9:32 dpdklab
2022-12-13  9:17 dpdklab
2022-12-13  9:17 dpdklab
2022-12-13  9:10 dpdklab
2022-12-13  9:04 dpdklab
2022-12-13  9:04 dpdklab
2022-12-13  9:04 dpdklab
2022-12-13  9:03 dpdklab
2022-12-13  8:54 dpdklab
2022-12-13  8:20 dpdklab
2022-12-13  8:20 dpdklab
2022-12-13  8:20 dpdklab
2022-12-13  8:19 dpdklab
2022-12-13  7:47 dpdklab
2022-12-13  7:36 dpdklab
2022-12-13  7:36 dpdklab
2022-12-13  7:36 dpdklab
2022-12-13  7:35 dpdklab
2022-12-13  7:11 dpdklab
2022-12-13  6:20 dpdklab
2022-12-13  6:16 dpdklab
2022-12-13  6:08 dpdklab
2022-12-13  6:04 dpdklab
2022-12-13  6:00 dpdklab
2022-12-13  5:54 dpdklab
2022-12-13  5:32 dpdklab
2022-12-13  4:56 dpdklab
2022-12-13  4:36 dpdklab
2022-12-13  4:36 dpdklab
2022-12-13  4:24 dpdklab
2022-12-13  4:01 dpdklab
2022-12-13  3: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=20221219055628.1AA104AF@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).