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| pw140336-140337 [PATCH] [2/2] net/nfp: support new firmwar
Date: Mon, 27 May 2024 20:10:23 -0700 (PDT)	[thread overview]
Message-ID: <66554b1f.630a0220.e4aa3.cc45SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240528012933.2345436-3-chaoyong.he@corigine.com>

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

_Functional Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tuesday, May 28 2024 01:29:33 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2dbb63594a9a985e2c8639b57f9fcd1468b9de97

140336-140337 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
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


Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-28  3:10 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240528012933.2345436-3-chaoyong.he@corigine.com>
2024-05-28  1:03 ` |SUCCESS| pw140336-140337 [PATCH 2/2] net/nfp: support new firmware name scheme qemudev
2024-05-28  1:07 ` qemudev
2024-05-28  1:30 ` |SUCCESS| pw140337 " checkpatch
2024-05-28  2:05 ` |SUCCESS| pw140336-140337 [PATCH] [2/2] net/nfp: support new firmwar dpdklab
2024-05-28  2:05 ` dpdklab
2024-05-28  2:06 ` dpdklab
2024-05-28  2:06 ` dpdklab
2024-05-28  2:06 ` dpdklab
2024-05-28  2:07 ` dpdklab
2024-05-28  2:07 ` dpdklab
2024-05-28  2:08 ` dpdklab
2024-05-28  2:08 ` dpdklab
2024-05-28  2:08 ` dpdklab
2024-05-28  2:09 ` dpdklab
2024-05-28  2:09 ` dpdklab
2024-05-28  2:09 ` dpdklab
2024-05-28  2:10 ` dpdklab
2024-05-28  2:10 ` dpdklab
2024-05-28  2:10 ` dpdklab
2024-05-28  2:10 ` dpdklab
2024-05-28  2:11 ` dpdklab
2024-05-28  2:11 ` dpdklab
2024-05-28  2:11 ` dpdklab
2024-05-28  2:12 ` dpdklab
2024-05-28  2:12 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:13 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:14 ` dpdklab
2024-05-28  2:15 ` dpdklab
2024-05-28  2:15 ` dpdklab
2024-05-28  2:17 ` dpdklab
2024-05-28  2:17 ` dpdklab
2024-05-28  2:23 ` |SUCCESS| pw140337 [PATCH 2/2] net/nfp: support new firmware name scheme 0-day Robot
2024-05-28  2:27 ` |SUCCESS| pw140336-140337 [PATCH] [2/2] net/nfp: support new firmwar dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:28 ` dpdklab
2024-05-28  2:29 ` dpdklab
2024-05-28  2:31 ` dpdklab
2024-05-28  2:31 ` dpdklab
2024-05-28  2:31 ` dpdklab
2024-05-28  2:32 ` dpdklab
2024-05-28  2:32 ` dpdklab
2024-05-28  2:32 ` dpdklab
2024-05-28  2:32 ` dpdklab
2024-05-28  2:33 ` dpdklab
2024-05-28  2:33 ` dpdklab
2024-05-28  2:33 ` dpdklab
2024-05-28  2:58 ` dpdklab
2024-05-28  2:59 ` dpdklab
2024-05-28  2:59 ` dpdklab
2024-05-28  2:59 ` dpdklab
2024-05-28  3:00 ` dpdklab
2024-05-28  3:00 ` dpdklab
2024-05-28  3:00 ` dpdklab
2024-05-28  3:01 ` dpdklab
2024-05-28  3:01 ` dpdklab
2024-05-28  3:01 ` dpdklab
2024-05-28  3:02 ` dpdklab
2024-05-28  3:05 ` dpdklab
2024-05-28  3:07 ` dpdklab
2024-05-28  3:07 ` dpdklab
2024-05-28  3:08 ` dpdklab
2024-05-28  3:08 ` dpdklab
2024-05-28  3:10 ` dpdklab
2024-05-28  3:10 ` dpdklab [this message]
2024-05-28  3:10 ` dpdklab
2024-05-28  3:11 ` dpdklab
2024-05-28  5:28 ` dpdklab
2024-05-28  5:39 ` dpdklab
2024-05-29 22:32 ` dpdklab
2024-05-29 22:32 ` dpdklab
2024-05-29 22:47 ` 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=66554b1f.630a0220.e4aa3.cc45SMTPIN_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).