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| pw135754 [PATCH] [v2] net/ice: add diagnostic support in T
Date: Fri, 05 Jan 2024 10:48:21 -0800 (PST)	[thread overview]
Message-ID: <65984ef5.170a0220.a5710.1ac5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Friday, January 05 2024 10:11:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

135754 --> 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/patchsets/28806/

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 18:48 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 18:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-05 23:58 dpdklab
2024-01-05 22:49 dpdklab
2024-01-05 22:10 dpdklab
2024-01-05 21:53 dpdklab
2024-01-05 21:44 dpdklab
2024-01-05 21:26 dpdklab
2024-01-05 21:23 dpdklab
2024-01-05 21:20 dpdklab
2024-01-05 20:58 dpdklab
2024-01-05 20:30 dpdklab
2024-01-05 20:30 dpdklab
2024-01-05 20:27 dpdklab
2024-01-05 20:24 dpdklab
2024-01-05 20:21 dpdklab
2024-01-05 20:21 dpdklab
2024-01-05 20:21 dpdklab
2024-01-05 20:18 dpdklab
2024-01-05 20:16 dpdklab
2024-01-05 20:09 dpdklab
2024-01-05 20:08 dpdklab
2024-01-05 20:08 dpdklab
2024-01-05 20:06 dpdklab
2024-01-05 20:05 dpdklab
2024-01-05 20:02 dpdklab
2024-01-05 20:02 dpdklab
2024-01-05 20:02 dpdklab
2024-01-05 20:00 dpdklab
2024-01-05 20:00 dpdklab
2024-01-05 19:59 dpdklab
2024-01-05 19:58 dpdklab
2024-01-05 19:57 dpdklab
2024-01-05 19:56 dpdklab
2024-01-05 19:54 dpdklab
2024-01-05 19:45 dpdklab
2024-01-05 19:43 dpdklab
2024-01-05 19:33 dpdklab
2024-01-05 19:33 dpdklab
2024-01-05 19:31 dpdklab
2024-01-05 19:30 dpdklab
2024-01-05 19:27 dpdklab
2024-01-05 19:23 dpdklab
2024-01-05 19:21 dpdklab
2024-01-05 19:18 dpdklab
2024-01-05 19:18 dpdklab
2024-01-05 19:13 dpdklab
2024-01-05 19:12 dpdklab
2024-01-05 19:09 dpdklab
2024-01-05 19:08 dpdklab
2024-01-05 19:06 dpdklab
2024-01-05 19:04 dpdklab
2024-01-05 19:00 dpdklab
2024-01-05 18:59 dpdklab
2024-01-05 18:59 dpdklab
2024-01-05 18:58 dpdklab
2024-01-05 18:58 dpdklab
2024-01-05 18:57 dpdklab
2024-01-05 18:53 dpdklab
2024-01-05 18:46 dpdklab
2024-01-05 18:45 dpdklab
2024-01-05 18:34 dpdklab
2024-01-05 18:34 dpdklab
2024-01-05 18:33 dpdklab
2024-01-05 18:21 dpdklab
2024-01-05 18:14 dpdklab
2024-01-05 18:08 dpdklab
2024-01-05 18:07 dpdklab
2024-01-05 18:07 dpdklab
2024-01-05 18:03 dpdklab
2024-01-05 17:59 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=65984ef5.170a0220.a5710.1ac5SMTPIN_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).