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, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] af1be4a055dd4a7d800f2b95e3ede53109e5c269
Date: Fri, 05 Jan 2024 15:02:32 -0800 (PST)	[thread overview]
Message-ID: <65988a88.170a0220.cc773.6bfdSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net-intel

af1be4a055dd4a7d800f2b95e3ede53109e5c269 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-05 23:02 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 23:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-06  6:46 dpdklab
2024-01-06  5:39 dpdklab
2024-01-06  3:36 dpdklab
2024-01-06  3:17 dpdklab
2024-01-06  1:20 dpdklab
2024-01-06  1:17 dpdklab
2024-01-06  0:37 dpdklab
2024-01-06  0:31 dpdklab
2024-01-06  0:26 dpdklab
2024-01-06  0:22 dpdklab
2024-01-06  0:22 dpdklab
2024-01-06  0:22 dpdklab
2024-01-06  0:22 dpdklab
2024-01-06  0:22 dpdklab
2024-01-06  0:21 dpdklab
2024-01-06  0:20 dpdklab
2024-01-06  0:16 dpdklab
2024-01-06  0:16 dpdklab
2024-01-06  0:16 dpdklab
2024-01-06  0:15 dpdklab
2024-01-06  0:15 dpdklab
2024-01-06  0:15 dpdklab
2024-01-06  0:15 dpdklab
2024-01-06  0:14 dpdklab
2024-01-06  0:14 dpdklab
2024-01-06  0:14 dpdklab
2024-01-06  0:13 dpdklab
2024-01-06  0:13 dpdklab
2024-01-06  0:13 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:12 dpdklab
2024-01-06  0:11 dpdklab
2024-01-06  0:11 dpdklab
2024-01-06  0:11 dpdklab
2024-01-06  0:10 dpdklab
2024-01-06  0:10 dpdklab
2024-01-06  0:09 dpdklab
2024-01-06  0:08 dpdklab
2024-01-06  0:08 dpdklab
2024-01-06  0:07 dpdklab
2024-01-06  0:00 dpdklab
2024-01-06  0:00 dpdklab
2024-01-06  0:00 dpdklab
2024-01-05 23:25 dpdklab
2024-01-05 23:03 dpdklab
2024-01-05 22:58 dpdklab
2024-01-05 22:58 dpdklab
2024-01-05 22:57 dpdklab
2024-01-05 22:56 dpdklab
2024-01-05 22:55 dpdklab
2024-01-05 22:55 dpdklab
2024-01-05 22:55 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=65988a88.170a0220.cc773.6bfdSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=qi.z.zhang@intel.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).