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| pw137370 [PATCH] common/cnxk: fix link cfg for sdp
Date: Thu, 29 Feb 2024 07:40:47 -0800 (PST)	[thread overview]
Message-ID: <65e0a57f.4a0a0220.fe696.565fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227185519.7711-1-hkalra@marvell.com>

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

_Functional Testing PASS_

Submitter: Harman Kalra <hkalra@marvell.com>
Date: Tuesday, February 27 2024 18:55:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ab5b7cd5a0b563e6d49be6c8beaad1f39c581a5c

137370 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.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-82
Compiler: gcc 11.4.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/1


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29298/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-29 15:40 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227185519.7711-1-hkalra@marvell.com>
2024-02-27 18:31 ` qemudev
2024-02-27 18:36 ` qemudev
2024-02-27 18:56 ` checkpatch
2024-02-27 19:45 ` 0-day Robot
2024-02-27 20:53 ` dpdklab
2024-02-27 20:55 ` dpdklab
2024-02-27 20:56 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 21:17 ` dpdklab
2024-02-27 21:18 ` dpdklab
2024-02-27 21:18 ` dpdklab
2024-02-27 21:18 ` dpdklab
2024-02-27 21:19 ` dpdklab
2024-02-27 21:19 ` dpdklab
2024-02-27 21:33 ` dpdklab
2024-02-27 21:33 ` dpdklab
2024-02-27 21:39 ` dpdklab
2024-02-27 21:49 ` dpdklab
2024-02-28  1:02 ` dpdklab
2024-02-28  1:02 ` dpdklab
2024-02-28  1:02 ` dpdklab
2024-02-28  1:02 ` dpdklab
2024-02-28  1:02 ` dpdklab
2024-02-28  1:02 ` dpdklab
2024-02-28  1:02 ` dpdklab
2024-02-28  1:03 ` dpdklab
2024-02-28  1:03 ` dpdklab
2024-02-28  1:08 ` dpdklab
2024-02-28  1:08 ` dpdklab
2024-02-28  1:09 ` dpdklab
2024-02-28  1:09 ` dpdklab
2024-02-28  1:10 ` dpdklab
2024-02-28  1:11 ` dpdklab
2024-02-28  1:11 ` dpdklab
2024-02-28  1:12 ` dpdklab
2024-02-28  1:12 ` dpdklab
2024-02-28  1:12 ` dpdklab
2024-02-28  1:12 ` dpdklab
2024-02-28  1:12 ` dpdklab
2024-02-28  1:13 ` dpdklab
2024-02-28  1:15 ` dpdklab
2024-02-28  1:15 ` dpdklab
2024-02-28  1:18 ` dpdklab
2024-02-28  1:20 ` dpdklab
2024-02-28  1:20 ` dpdklab
2024-02-28  1:21 ` dpdklab
2024-02-28  1:21 ` dpdklab
2024-02-28  1:29 ` dpdklab
2024-02-28  1:30 ` dpdklab
2024-02-28  1:30 ` dpdklab
2024-02-28  1:36 ` dpdklab
2024-02-28  1:38 ` dpdklab
2024-02-28  1:40 ` dpdklab
2024-02-28  1:40 ` dpdklab
2024-02-28  2:11 ` dpdklab
2024-02-28  2:12 ` dpdklab
2024-02-28  2:13 ` dpdklab
2024-02-28  2:16 ` dpdklab
2024-02-28  2:23 ` dpdklab
2024-02-28  2:25 ` dpdklab
2024-02-28  2:39 ` dpdklab
2024-02-28  3:00 ` dpdklab
2024-02-28  4:07 ` dpdklab
2024-02-28  4:08 ` dpdklab
2024-02-28  9:19 ` dpdklab
2024-02-28 12:14 ` dpdklab
2024-02-28 12:26 ` dpdklab
2024-02-28 20:13 ` dpdklab
2024-02-29 11:47 ` dpdklab
2024-02-29 15:28 ` dpdklab
2024-02-29 15:36 ` dpdklab
2024-02-29 15:40 ` dpdklab [this message]
2024-02-29 15:43 ` 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=65e0a57f.4a0a0220.fe696.565fSMTPIN_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).