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| pw137655-137657 [PATCH] [v2,3/3] net/nfp: add force reload
Date: Fri, 01 Mar 2024 13:31:59 -0800 (PST)	[thread overview]
Message-ID: <65e2494f.170a0220.a00e0.abf9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301084244.190484-4-chaoyong.he@corigine.com>

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

_Functional Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, March 01 2024 08:42:44 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d4d5bbe6791850987d6d28da675574a868e8274c

137655-137657 --> 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/29363/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-01 21:32 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301084244.190484-4-chaoyong.he@corigine.com>
2024-03-01  8:35 ` |SUCCESS| pw137655-137657 [PATCH v2 3/3] net/nfp: add force reload firmware option qemudev
2024-03-01  8:40 ` qemudev
2024-03-01  8:45 ` |SUCCESS| pw137657 " checkpatch
2024-03-01  9:45 ` 0-day Robot
2024-03-01 16:56 ` |SUCCESS| pw137655-137657 [PATCH] [v2,3/3] net/nfp: add force reload dpdklab
2024-03-01 17:08 ` dpdklab
2024-03-01 17:09 ` |FAILURE| " dpdklab
2024-03-01 17:13 ` dpdklab
2024-03-01 17:39 ` |SUCCESS| " dpdklab
2024-03-01 17:53 ` |FAILURE| " dpdklab
2024-03-01 17:54 ` |SUCCESS| " dpdklab
2024-03-01 17:56 ` dpdklab
2024-03-01 17:57 ` dpdklab
2024-03-01 17:57 ` dpdklab
2024-03-01 17:57 ` dpdklab
2024-03-01 17:58 ` dpdklab
2024-03-01 18:03 ` dpdklab
2024-03-01 18:05 ` dpdklab
2024-03-01 18:06 ` dpdklab
2024-03-01 18:07 ` dpdklab
2024-03-01 20:10 ` dpdklab
2024-03-01 20:11 ` dpdklab
2024-03-01 20:15 ` dpdklab
2024-03-01 20:15 ` dpdklab
2024-03-01 20:16 ` dpdklab
2024-03-01 20:16 ` dpdklab
2024-03-01 20:18 ` dpdklab
2024-03-01 20:19 ` dpdklab
2024-03-01 20:19 ` dpdklab
2024-03-01 20:19 ` dpdklab
2024-03-01 20:20 ` dpdklab
2024-03-01 20:20 ` dpdklab
2024-03-01 20:21 ` dpdklab
2024-03-01 20:26 ` dpdklab
2024-03-01 20:27 ` dpdklab
2024-03-01 20:34 ` dpdklab
2024-03-01 20:35 ` dpdklab
2024-03-01 20:46 ` dpdklab
2024-03-01 20:48 ` dpdklab
2024-03-01 20:48 ` dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:49 ` dpdklab
2024-03-01 20:51 ` dpdklab
2024-03-01 20:54 ` dpdklab
2024-03-01 20:55 ` dpdklab
2024-03-01 20:55 ` dpdklab
2024-03-01 20:56 ` dpdklab
2024-03-01 20:59 ` dpdklab
2024-03-01 21:00 ` dpdklab
2024-03-01 21:00 ` dpdklab
2024-03-01 21:01 ` dpdklab
2024-03-01 21:02 ` dpdklab
2024-03-01 21:03 ` dpdklab
2024-03-01 21:04 ` dpdklab
2024-03-01 21:05 ` dpdklab
2024-03-01 21:05 ` dpdklab
2024-03-01 21:05 ` dpdklab
2024-03-01 21:06 ` dpdklab
2024-03-01 21:14 ` dpdklab
2024-03-01 21:14 ` dpdklab
2024-03-01 21:25 ` dpdklab
2024-03-01 21:31 ` dpdklab [this message]
2024-03-01 21:33 ` |FAILURE| " dpdklab
2024-03-01 21:35 ` |SUCCESS| " dpdklab
2024-03-01 21:49 ` dpdklab
2024-03-01 22:25 ` dpdklab
2024-03-01 22:27 ` dpdklab
2024-03-02  1:19 ` dpdklab
2024-03-02  1:21 ` dpdklab
2024-03-02  2:02 ` dpdklab
2024-03-02 22:58 ` dpdklab
2024-03-05 14:55 ` dpdklab
2024-03-05 15:33 ` dpdklab
2024-03-05 15:57 ` 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=65e2494f.170a0220.a00e0.abf9SMTPIN_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).