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] fcd039e4663bf2b595d7af3a8175a3e0bc09b367
Date: Thu,  5 May 2022 01:41:51 -0400 (EDT)	[thread overview]
Message-ID: <20220505054151.EA1EFA77C@noxus.dpdklab.iol.unh.edu> (raw)

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

_Functional Testing PASS_

Branch: tags/v21.11

fcd039e4663bf2b595d7af3a8175a3e0bc09b367 --> 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/19678/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-05-05  5:41 UTC|newest]

Thread overview: 148+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  5:41 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-10  7:01 dpdklab
2022-05-10  6:55 dpdklab
2022-05-10  6:36 dpdklab
2022-05-10  5:41 dpdklab
2022-05-10  5:35 dpdklab
2022-05-10  5:29 dpdklab
2022-05-10  5:22 dpdklab
2022-05-10  5:09 dpdklab
2022-05-10  5:08 dpdklab
2022-05-10  0:15 dpdklab
2022-05-09 18:14 dpdklab
2022-05-09 10:18 dpdklab
2022-05-09  8:09 dpdklab
2022-05-09  6:04 dpdklab
2022-05-09  5:53 dpdklab
2022-05-09  5:52 dpdklab
2022-05-09  5:37 dpdklab
2022-05-09  5:14 dpdklab
2022-05-09  5:01 dpdklab
2022-05-08 21:16 dpdklab
2022-05-08 10:59 dpdklab
2022-05-08  7:09 dpdklab
2022-05-08  5:41 dpdklab
2022-05-08  5:33 dpdklab
2022-05-08  5:21 dpdklab
2022-05-08  5:17 dpdklab
2022-05-08  5:09 dpdklab
2022-05-08  5:08 dpdklab
2022-05-07 16:23 dpdklab
2022-05-07  8:09 dpdklab
2022-05-07  5:40 dpdklab
2022-05-07  5:33 dpdklab
2022-05-07  5:28 dpdklab
2022-05-07  5:17 dpdklab
2022-05-07  5:09 dpdklab
2022-05-07  5:07 dpdklab
2022-05-06 23:56 dpdklab
2022-05-06 11:31 dpdklab
2022-05-06  8:35 dpdklab
2022-05-06  5:41 dpdklab
2022-05-06  5:33 dpdklab
2022-05-06  5:21 dpdklab
2022-05-06  5:17 dpdklab
2022-05-06  5:10 dpdklab
2022-05-06  5:07 dpdklab
2022-05-05  8:30 dpdklab
2022-05-05  8:29 dpdklab
2022-05-05  8:03 dpdklab
2022-05-05  5:33 dpdklab
2022-05-05  5:29 dpdklab
2022-05-05  5:17 dpdklab
2022-05-05  5:08 dpdklab
2022-05-05  5:08 dpdklab
2022-05-04  8:05 dpdklab
2022-05-04  7:41 dpdklab
2022-05-04  7:39 dpdklab
2022-05-04  5:40 dpdklab
2022-05-04  5:34 dpdklab
2022-05-04  5:21 dpdklab
2022-05-04  5:17 dpdklab
2022-05-04  5:10 dpdklab
2022-05-04  5:08 dpdklab
2022-05-03 15:59 dpdklab
2022-05-03 11:20 dpdklab
2022-05-03  8:21 dpdklab
2022-05-03  6:07 dpdklab
2022-05-03  5:56 dpdklab
2022-05-03  5:47 dpdklab
2022-05-03  5:40 dpdklab
2022-05-03  5:30 dpdklab
2022-05-03  5:22 dpdklab
2022-05-02 16:20 dpdklab
2022-05-02  8:40 dpdklab
2022-05-02  8:18 dpdklab
2022-05-02  8:16 dpdklab
2022-05-02  7:50 dpdklab
2022-05-02  5:41 dpdklab
2022-05-02  5:34 dpdklab
2022-05-02  5:21 dpdklab
2022-05-02  5:18 dpdklab
2022-05-02  5:09 dpdklab
2022-05-02  5:08 dpdklab
2022-05-02  4:14 dpdklab
2022-05-02  1:40 dpdklab
2022-05-01 10:02 dpdklab
2022-05-01  9:18 dpdklab
2022-05-01  8:38 dpdklab
2022-05-01  8:16 dpdklab
2022-05-01  8:12 dpdklab
2022-05-01  5:40 dpdklab
2022-05-01  5:34 dpdklab
2022-05-01  5:20 dpdklab
2022-05-01  5:18 dpdklab
2022-05-01  5:08 dpdklab
2022-05-01  5:07 dpdklab
2022-04-30 20:12 dpdklab
2022-04-30 15:30 dpdklab
2022-04-30 14:47 dpdklab
2022-04-30 11:05 dpdklab
2022-04-30  8:29 dpdklab
2022-04-30  5:42 dpdklab
2022-04-30  5:34 dpdklab
2022-04-30  5:30 dpdklab
2022-04-30  5:23 dpdklab
2022-04-30  5:11 dpdklab
2022-04-30  5:08 dpdklab
2022-04-29 19:41 dpdklab
2022-04-29 19:12 dpdklab
2022-04-29 14:06 dpdklab
2022-04-29 13:55 dpdklab
2022-04-29  9:04 dpdklab
2022-04-29  8:13 dpdklab
2022-04-29  5:41 dpdklab
2022-04-29  5:33 dpdklab
2022-04-29  5:21 dpdklab
2022-04-29  5:17 dpdklab
2022-04-29  5:08 dpdklab
2022-04-29  5:08 dpdklab
2022-04-28 20:01 dpdklab
2022-04-28 18:44 dpdklab
2022-04-28 18:35 dpdklab
2022-04-28  7:04 dpdklab
2022-04-28  5:41 dpdklab
2022-04-28  5:33 dpdklab
2022-04-28  5:21 dpdklab
2022-04-28  5:17 dpdklab
2022-04-28  5:09 dpdklab
2022-04-28  5:08 dpdklab
2022-04-27  6:05 dpdklab
2022-04-27  6:05 dpdklab
2022-04-27  5:49 dpdklab
2022-04-27  5:41 dpdklab
2022-04-27  5:38 dpdklab
2022-04-27  5:33 dpdklab
2022-04-27  5:21 dpdklab
2022-04-27  5:17 dpdklab
2022-04-27  5:09 dpdklab
2022-04-27  5:07 dpdklab
2022-04-27  4:11 dpdklab
2022-04-27  3:46 dpdklab
2022-04-27  3:43 dpdklab
2022-04-27  3:31 dpdklab
2022-04-27  3:21 dpdklab
2022-04-27  3:17 dpdklab
2022-04-27  3:02 dpdklab
2022-04-27  3:01 dpdklab
2022-04-27  2:56 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=20220505054151.EA1EFA77C@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).