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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] e760c2031e005e855436f756eec67d5390ad1f4a
Date: Tue, 07 Nov 2023 12:56:31 -0800 (PST)	[thread overview]
Message-ID: <654aa47f.250a0220.2d831.5388SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net

e760c2031e005e855436f756eec67d5390ad1f4a --> 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 XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-07 20:56 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 20:56 dpdklab [this message]
2023-11-07 20:56 dpdklab
2023-11-07 21:21 dpdklab
2023-11-07 21:21 dpdklab
2023-11-07 21:22 dpdklab
2023-11-07 21:24 dpdklab
2023-11-07 21:27 dpdklab
2023-11-07 21:30 dpdklab
2023-11-07 21:32 dpdklab
2023-11-07 21:43 dpdklab
2023-11-07 23:21 dpdklab
2023-11-07 23:21 dpdklab
2023-11-07 23:22 dpdklab
2023-11-07 23:22 dpdklab
2023-11-07 23:22 dpdklab
2023-11-07 23:23 dpdklab
2023-11-07 23:23 dpdklab
2023-11-07 23:24 dpdklab
2023-11-07 23:28 dpdklab
2023-11-07 23:28 dpdklab
2023-11-07 23:28 dpdklab
2023-11-07 23:28 dpdklab
2023-11-07 23:29 dpdklab
2023-11-07 23:29 dpdklab
2023-11-07 23:30 dpdklab
2023-11-07 23:30 dpdklab
2023-11-07 23:44 dpdklab
2023-11-07 23:45 dpdklab
2023-11-07 23:46 dpdklab
2023-11-07 23:46 dpdklab
2023-11-08  0:15 dpdklab
2023-11-08  0:15 dpdklab
2023-11-08  0:16 dpdklab
2023-11-08  0:16 dpdklab
2023-11-08  0:16 dpdklab
2023-11-08  0:16 dpdklab
2023-11-08  0:25 dpdklab
2023-11-08  0:26 dpdklab
2023-11-08  0:29 dpdklab
2023-11-08  0:33 dpdklab
2023-11-08  0:34 dpdklab
2023-11-08  0:34 dpdklab
2023-11-08  0:34 dpdklab
2023-11-08  0:34 dpdklab
2023-11-08  0:34 dpdklab
2023-11-08  0:35 dpdklab
2023-11-08  0:35 dpdklab
2023-11-08  0:41 dpdklab
2023-11-08  0:49 dpdklab
2023-11-08  1:24 dpdklab
2023-11-08  1:55 dpdklab
2023-11-08  2:32 dpdklab
2023-11-08  8:37 dpdklab
2023-11-08 11:42 dpdklab
2023-11-08 20:59 dpdklab
2023-11-08 21:22 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=654aa47f.250a0220.2d831.5388SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.com \
    --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).