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
Subject: |SUCCESS| [GIT MASTER] 132173c4169322487a9041a450b9d3860de0a434
Date: Fri, 23 Jun 2023 14:48:27 -0700 (PDT)	[thread overview]
Message-ID: <6496132b.050a0220.e32bd.1d5eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk

132173c4169322487a9041a450b9d3860de0a434 --> functional testing pass

Test environment and result as below:

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


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/4


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-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/25149/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-23 21:48 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 21:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-26 14:57 dpdklab
2023-06-26 14:46 dpdklab
2023-06-26 14:08 dpdklab
2023-06-26 13:54 dpdklab
2023-06-25  3:40 dpdklab
2023-06-25  2:06 dpdklab
2023-06-25  1:58 dpdklab
2023-06-25  1:58 dpdklab
2023-06-25  1:56 dpdklab
2023-06-25  1:54 dpdklab
2023-06-25  1:53 dpdklab
2023-06-25  1:48 dpdklab
2023-06-25  1:47 dpdklab
2023-06-25  1:44 dpdklab
2023-06-25  1:44 dpdklab
2023-06-25  1:40 dpdklab
2023-06-25  1:39 dpdklab
2023-06-25  1:30 dpdklab
2023-06-25  1:28 dpdklab
2023-06-25  1:28 dpdklab
2023-06-25  1:28 dpdklab
2023-06-25  1:27 dpdklab
2023-06-25  1:26 dpdklab
2023-06-25  1:19 dpdklab
2023-06-25  1:12 dpdklab
2023-06-25  1:12 dpdklab
2023-06-25  1:12 dpdklab
2023-06-25  1:03 dpdklab
2023-06-25  1:02 dpdklab
2023-06-25  1:01 dpdklab
2023-06-25  1:01 dpdklab
2023-06-24  8:25 dpdklab
2023-06-24  5:22 dpdklab
2023-06-24  2:10 dpdklab
2023-06-24  2:09 dpdklab
2023-06-24  2:05 dpdklab
2023-06-24  2:00 dpdklab
2023-06-24  1:57 dpdklab
2023-06-24  1:53 dpdklab
2023-06-24  1:53 dpdklab
2023-06-24  1:43 dpdklab
2023-06-24  1:41 dpdklab
2023-06-24  1:41 dpdklab
2023-06-24  1:40 dpdklab
2023-06-24  1:40 dpdklab
2023-06-24  1:37 dpdklab
2023-06-24  1:36 dpdklab
2023-06-24  1:36 dpdklab
2023-06-24  1:35 dpdklab
2023-06-24  1:27 dpdklab
2023-06-24  1:25 dpdklab
2023-06-24  1:20 dpdklab
2023-06-24  1:17 dpdklab
2023-06-24  1:10 dpdklab
2023-06-24  1:09 dpdklab
2023-06-24  1:04 dpdklab
2023-06-24  1:03 dpdklab
2023-06-24  1:00 dpdklab
2023-06-24  0:58 dpdklab
2023-06-24  0:58 dpdklab
2023-06-23 23:19 dpdklab
2023-06-23 21:43 dpdklab
2023-06-23 21:39 dpdklab
2023-06-23 21:29 dpdklab
2023-06-23 21:13 dpdklab
2023-06-23 21:02 dpdklab
2023-06-23 21:00 dpdklab
2023-06-23 20:54 dpdklab
2023-06-23 20:48 dpdklab
2023-06-23 20:44 dpdklab
2023-06-23 20:41 dpdklab
2023-06-23 20:31 dpdklab
2023-06-23 20:30 dpdklab
2023-06-23 20:21 dpdklab
2023-06-23 20:19 dpdklab
2023-06-23 20:19 dpdklab
2023-06-23 20:08 dpdklab
2023-06-23 20:07 dpdklab
2023-06-23 20:05 dpdklab
2023-06-23 19:56 dpdklab
2023-06-23 19:55 dpdklab
2023-06-23 19:49 dpdklab
2023-06-23 19:48 dpdklab
2023-06-23 19:48 dpdklab
2023-06-23 19:48 dpdklab
2023-06-23 19:47 dpdklab
2023-06-23 19:47 dpdklab
2023-06-23 19:47 dpdklab
2023-06-23 19:47 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=6496132b.050a0220.e32bd.1d5eSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    /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).