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] 7faf9ad3c41bea806c9222110cdecd04d7db8bfe
Date: Tue, 21 Mar 2023 05:22:01 +0000 (UTC)	[thread overview]
Message-ID: <20230321052201.BEC3560214@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

_Functional Testing PASS_

Branch: tags/v21.11

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


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-21  5:22 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21  5:22 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-24 10:39 dpdklab
2023-03-24  5:36 dpdklab
2023-03-24  3:48 dpdklab
2023-03-23 17:29 dpdklab
2023-03-23 15:57 dpdklab
2023-03-23 12:37 dpdklab
2023-03-23  7:42 dpdklab
2023-03-22 18:58 dpdklab
2023-03-22 14:03 dpdklab
2023-03-22 13:56 dpdklab
2023-03-22 13:41 dpdklab
2023-03-22  6:15 dpdklab
2023-03-22  5:22 dpdklab
2023-03-22  5:15 dpdklab
2023-03-22  5:11 dpdklab
2023-03-22  5:10 dpdklab
2023-03-22  5:04 dpdklab
2023-03-22  5:04 dpdklab
2023-03-22  5:03 dpdklab
2023-03-22  4:59 dpdklab
2023-03-22  4:57 dpdklab
2023-03-21 23:29 dpdklab
2023-03-21 23:00 dpdklab
2023-03-21 19:56 dpdklab
2023-03-21 19:55 dpdklab
2023-03-21 19:54 dpdklab
2023-03-21 16:28 dpdklab
2023-03-21 10:47 dpdklab
2023-03-21  9:33 dpdklab
2023-03-21  5:18 dpdklab
2023-03-21  5:17 dpdklab
2023-03-21  5:13 dpdklab
2023-03-21  5:09 dpdklab
2023-03-21  5:06 dpdklab
2023-03-21  5:04 dpdklab
2023-03-21  5:03 dpdklab
2023-03-21  5:03 dpdklab
2023-03-21  4:57 dpdklab
2023-03-21  4:55 dpdklab
2023-03-21  4:54 dpdklab
2023-03-21  4:50 dpdklab
2023-03-21  3:24 dpdklab
2023-03-21  3:20 dpdklab
2023-03-21  3:19 dpdklab
2023-03-21  3:13 dpdklab
2023-03-21  3:11 dpdklab
2023-03-21  3:08 dpdklab
2023-03-21  3:08 dpdklab
2023-03-21  3:06 dpdklab
2023-03-21  3:05 dpdklab
2023-03-21  3:04 dpdklab
2023-03-21  3:00 dpdklab
2023-03-21  2:57 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=20230321052201.BEC3560214@dpdk-ubuntu.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).