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| pw137660 [PATCH] [v5] net/i40e: add diagnostic support in
Date: Tue, 05 Mar 2024 02:06:29 -0800 (PST)	[thread overview]
Message-ID: <65e6eea5.620a0220.d5c49.0f03SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301094422.460012-1-mingjinx.ye@intel.com>

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

_Functional Testing PASS_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Friday, March 01 2024 09:44:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3408b132b31906fe1ed28d6b2009b98202e1cff0

137660 --> 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/29366/

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-05 10:06 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301094422.460012-1-mingjinx.ye@intel.com>
2024-03-01 10:04 ` |SUCCESS| pw137660 [PATCH v5] net/i40e: add diagnostic support in TX path checkpatch
2024-03-01 11:05 ` 0-day Robot
2024-03-01 15:17 ` |SUCCESS| pw137660 [PATCH] [v5] net/i40e: add diagnostic support in dpdklab
2024-03-01 15:21 ` |FAILURE| " dpdklab
2024-03-01 15:48 ` |SUCCESS| " dpdklab
2024-03-01 15:58 ` |FAILURE| " dpdklab
2024-03-01 15:59 ` |SUCCESS| " dpdklab
2024-03-01 16:00 ` dpdklab
2024-03-01 16:09 ` dpdklab
2024-03-01 16:10 ` dpdklab
2024-03-01 16:11 ` dpdklab
2024-03-01 16:11 ` dpdklab
2024-03-01 16:14 ` dpdklab
2024-03-01 16:16 ` dpdklab
2024-03-01 16:28 ` dpdklab
2024-03-01 16:35 ` |FAILURE| " dpdklab
2024-03-01 16:38 ` |SUCCESS| " dpdklab
2024-03-01 16:43 ` dpdklab
2024-03-01 16:44 ` dpdklab
2024-03-01 16:45 ` dpdklab
2024-03-01 18:07 ` |FAILURE| " dpdklab
2024-03-01 18:17 ` |SUCCESS| " dpdklab
2024-03-01 18:27 ` dpdklab
2024-03-01 18:27 ` dpdklab
2024-03-01 18:28 ` dpdklab
2024-03-01 18:28 ` dpdklab
2024-03-01 18:30 ` dpdklab
2024-03-01 18:31 ` dpdklab
2024-03-01 18:32 ` dpdklab
2024-03-01 18:32 ` dpdklab
2024-03-01 18:36 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:37 ` dpdklab
2024-03-01 18:38 ` dpdklab
2024-03-01 18:38 ` dpdklab
2024-03-01 18:39 ` dpdklab
2024-03-01 18:39 ` dpdklab
2024-03-01 18:39 ` dpdklab
2024-03-01 18:40 ` dpdklab
2024-03-01 18:40 ` dpdklab
2024-03-01 18:40 ` dpdklab
2024-03-01 18:40 ` dpdklab
2024-03-01 18:41 ` dpdklab
2024-03-01 18:41 ` dpdklab
2024-03-01 18:41 ` dpdklab
2024-03-01 18:41 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:42 ` dpdklab
2024-03-01 18:43 ` dpdklab
2024-03-01 18:43 ` dpdklab
2024-03-01 18:43 ` dpdklab
2024-03-01 18:43 ` dpdklab
2024-03-01 18:44 ` dpdklab
2024-03-01 18:46 ` dpdklab
2024-03-01 18:46 ` dpdklab
2024-03-01 18:46 ` dpdklab
2024-03-01 18:48 ` dpdklab
2024-03-01 18:57 ` dpdklab
2024-03-01 19:09 ` dpdklab
2024-03-01 19:15 ` dpdklab
2024-03-01 19:54 ` dpdklab
2024-03-01 19:58 ` dpdklab
2024-03-01 20:03 ` |FAILURE| " dpdklab
2024-03-01 20:09 ` |SUCCESS| " dpdklab
2024-03-01 21:54 ` dpdklab
2024-03-01 22:29 ` dpdklab
2024-03-02  1:56 ` dpdklab
2024-03-02  2:03 ` dpdklab
2024-03-02  6:33 ` |SUCCESS| pw137660 [PATCH v5] net/i40e: add diagnostic support in TX path qemudev
2024-03-02  6:37 ` qemudev
2024-03-02 20:11 ` |SUCCESS| pw137660 [PATCH] [v5] net/i40e: add diagnostic support in dpdklab
2024-03-05  9:45 ` dpdklab
2024-03-05 10:06 ` dpdklab [this message]
2024-03-05 10:30 ` 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=65e6eea5.620a0220.d5c49.0f03SMTPIN_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).