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] b941165a0060ba60672d70a7002434ebfc7b2a7e
Date: Mon, 18 Jul 2022 02:04:40 -0400 (EDT)	[thread overview]
Message-ID: <20220718060440.502A210618C@noxus.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing PASS_

Branch: tags/v21.11

b941165a0060ba60672d70a7002434ebfc7b2a7e --> 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


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
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/20781/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-07-18  6:04 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  6:04 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-18  7:44 dpdklab
2022-07-18  7:02 dpdklab
2022-07-18  6:44 dpdklab
2022-07-18  6:39 dpdklab
2022-07-18  5:57 dpdklab
2022-07-18  5:53 dpdklab
2022-07-18  5:52 dpdklab
2022-07-18  5:37 dpdklab
2022-07-18  5:29 dpdklab
2022-07-18  5:12 dpdklab
2022-07-17  6:49 dpdklab
2022-07-17  6:17 dpdklab
2022-07-17  6:02 dpdklab
2022-07-17  5:43 dpdklab
2022-07-17  5:41 dpdklab
2022-07-17  5:35 dpdklab
2022-07-17  5:31 dpdklab
2022-07-17  5:19 dpdklab
2022-07-17  5:17 dpdklab
2022-07-17  5:12 dpdklab
2022-07-16  7:11 dpdklab
2022-07-16  6:22 dpdklab
2022-07-16  6:22 dpdklab
2022-07-16  6:11 dpdklab
2022-07-16  5:52 dpdklab
2022-07-16  5:44 dpdklab
2022-07-16  5:35 dpdklab
2022-07-16  5:23 dpdklab
2022-07-16  5:19 dpdklab
2022-07-16  5:18 dpdklab
2022-07-16  5:17 dpdklab
2022-07-15  7:02 dpdklab
2022-07-15  6:40 dpdklab
2022-07-15  6:28 dpdklab
2022-07-15  6:15 dpdklab
2022-07-15  6:03 dpdklab
2022-07-15  5:43 dpdklab
2022-07-15  5:35 dpdklab
2022-07-15  5:31 dpdklab
2022-07-15  5:19 dpdklab
2022-07-15  5:14 dpdklab
2022-07-15  5:11 dpdklab
2022-07-14  6:50 dpdklab
2022-07-14  6:45 dpdklab
2022-07-14  6:40 dpdklab
2022-07-14  6:27 dpdklab
2022-07-14  6:23 dpdklab
2022-07-14  5:44 dpdklab
2022-07-14  5:37 dpdklab
2022-07-14  5:25 dpdklab
2022-07-14  5:23 dpdklab
2022-07-14  5:22 dpdklab
2022-07-14  5:15 dpdklab
2022-07-13  6:31 dpdklab
2022-07-13  6:24 dpdklab
2022-07-13  6:01 dpdklab
2022-07-13  6:01 dpdklab
2022-07-13  5:46 dpdklab
2022-07-13  5:45 dpdklab
2022-07-13  5:43 dpdklab
2022-07-13  5:33 dpdklab
2022-07-13  5:25 dpdklab
2022-07-13  5:16 dpdklab
2022-07-13  5:12 dpdklab
2022-07-13  3:59 dpdklab
2022-07-13  3:59 dpdklab
2022-07-13  3:45 dpdklab
2022-07-13  3:35 dpdklab
2022-07-13  3:22 dpdklab
2022-07-13  3:20 dpdklab
2022-07-13  3:19 dpdklab
2022-07-13  3:10 dpdklab
2022-07-13  3:04 dpdklab
2022-07-13  3:03 dpdklab
2022-07-13  2:59 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=20220718060440.502A210618C@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).