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| pw135620-135622 [PATCH] [v5,3/3] net/iavf: add Tx LLDP com
Date: Thu, 28 Dec 2023 07:37:52 -0800 (PST)	[thread overview]
Message-ID: <658d9650.050a0220.a1c7d.0224SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135622

_Functional Testing PASS_

Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Thursday, December 28 2023 03:22:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

135620-135622 --> 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


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/patchsets/28747/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-28 15:37 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 15:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-28 17:50 dpdklab
2023-12-28 17:25 dpdklab
2023-12-28 16:24 dpdklab
2023-12-28 16:01 dpdklab
2023-12-28 15:51 dpdklab
2023-12-28 15:51 dpdklab
2023-12-28 15:49 dpdklab
2023-12-28 15:47 dpdklab
2023-12-28 15:44 dpdklab
2023-12-28 15:42 dpdklab
2023-12-28 15:39 dpdklab
2023-12-28 15:39 dpdklab
2023-12-28 15:38 dpdklab
2023-12-28 15:38 dpdklab
2023-12-28 15:37 dpdklab
2023-12-28 15:35 dpdklab
2023-12-28 15:34 dpdklab
2023-12-28 15:34 dpdklab
2023-12-28 15:32 dpdklab
2023-12-28 15:31 dpdklab
2023-12-28 15:30 dpdklab
2023-12-28 15:30 dpdklab
2023-12-28 15:29 dpdklab
2023-12-28 15:29 dpdklab
2023-12-28 15:29 dpdklab
2023-12-28 15:29 dpdklab
2023-12-28 15:29 dpdklab
2023-12-28 15:28 dpdklab
2023-12-28 15:26 dpdklab
2023-12-28 15:26 dpdklab
2023-12-28 15:26 dpdklab
2023-12-28 15:25 dpdklab
2023-12-28 15:25 dpdklab
2023-12-28 15:24 dpdklab
2023-12-28 15:23 dpdklab
2023-12-28 15:22 dpdklab
2023-12-28 15:18 dpdklab
2023-12-28 15:18 dpdklab
2023-12-28 15:17 dpdklab
2023-12-28 15:09 dpdklab
2023-12-28 15:05 dpdklab
2023-12-28 15:04 dpdklab
2023-12-28 15:03 dpdklab
2023-12-28 15:00 dpdklab
2023-12-28 14:59 dpdklab
2023-12-28 14:59 dpdklab
2023-12-28 14:58 dpdklab
2023-12-28 14:51 dpdklab
2023-12-28 14:51 dpdklab
2023-12-28 14:50 dpdklab
2023-12-28 14:49 dpdklab
2023-12-28 14:48 dpdklab
2023-12-28 14:48 dpdklab
2023-12-28 14:47 dpdklab
2023-12-28 14:46 dpdklab
2023-12-28 14:46 dpdklab
2023-12-28 14:46 dpdklab
2023-12-28 14:45 dpdklab
2023-12-28 14:36 dpdklab
2023-12-28 14:36 dpdklab
2023-12-28 14:29 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=658d9650.050a0220.a1c7d.0224SMTPIN_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).