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] 915ecb9cd68c5d613bee44ad41536a4f489f6d15
Date: Thu, 04 Jan 2024 13:43:16 -0800 (PST)	[thread overview]
Message-ID: <65972674.050a0220.d1fec.0a29SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net-intel

915ecb9cd68c5d613bee44ad41536a4f489f6d15 --> functional testing pass

Test environment and result as below:

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


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


Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-04 21:43 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 21:43 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-05  8:27 dpdklab
2024-01-05  8:18 dpdklab
2024-01-05  0:55 dpdklab
2024-01-05  0:49 dpdklab
2024-01-04 23:34 dpdklab
2024-01-04 23:16 dpdklab
2024-01-04 22:32 dpdklab
2024-01-04 22:25 dpdklab
2024-01-04 22:23 dpdklab
2024-01-04 22:19 dpdklab
2024-01-04 22:19 dpdklab
2024-01-04 22:18 dpdklab
2024-01-04 22:16 dpdklab
2024-01-04 22:15 dpdklab
2024-01-04 22:15 dpdklab
2024-01-04 22:14 dpdklab
2024-01-04 22:14 dpdklab
2024-01-04 22:13 dpdklab
2024-01-04 22:11 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:10 dpdklab
2024-01-04 22:09 dpdklab
2024-01-04 22:08 dpdklab
2024-01-04 22:08 dpdklab
2024-01-04 22:08 dpdklab
2024-01-04 22:07 dpdklab
2024-01-04 22:06 dpdklab
2024-01-04 22:06 dpdklab
2024-01-04 22:05 dpdklab
2024-01-04 22:03 dpdklab
2024-01-04 22:03 dpdklab
2024-01-04 22:02 dpdklab
2024-01-04 22:02 dpdklab
2024-01-04 22:01 dpdklab
2024-01-04 22:01 dpdklab
2024-01-04 22:00 dpdklab
2024-01-04 22:00 dpdklab
2024-01-04 22:00 dpdklab
2024-01-04 21:59 dpdklab
2024-01-04 21:57 dpdklab
2024-01-04 21:47 dpdklab
2024-01-04 21:46 dpdklab
2024-01-04 21:45 dpdklab
2024-01-04 21:44 dpdklab
2024-01-04 21:42 dpdklab
2024-01-04 21:39 dpdklab
2024-01-04 21:38 dpdklab
2024-01-04 21:38 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=65972674.050a0220.d1fec.0a29SMTPIN_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).