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| pw138133 [PATCH] [v2] add a ignore list for get_maintainer
Date: Wed, 13 Mar 2024 10:47:12 -0700 (PDT)	[thread overview]
Message-ID: <65f1e6a0.020a0220.c3fb4.2892SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240308181310.70014-1-stephen@networkplumber.org>

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, March 08 2024 18:12:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138133 --> 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


Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.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/29483/

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-13 17:47 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308181310.70014-1-stephen@networkplumber.org>
2024-03-08 17:53 ` |SUCCESS| pw138133 [PATCH v2] " qemudev
2024-03-08 17:58 ` qemudev
2024-03-08 18:13 ` |WARNING| " checkpatch
2024-03-08 19:03 ` |SUCCESS| " 0-day Robot
2024-03-08 22:27 ` |SUCCESS| pw138133 [PATCH] [v2] " dpdklab
2024-03-08 22:31 ` dpdklab
2024-03-08 22:33 ` dpdklab
2024-03-08 22:43 ` dpdklab
2024-03-08 22:53 ` dpdklab
2024-03-08 22:57 ` dpdklab
2024-03-08 22:57 ` dpdklab
2024-03-08 22:59 ` dpdklab
2024-03-08 23:01 ` dpdklab
2024-03-08 23:02 ` dpdklab
2024-03-08 23:04 ` dpdklab
2024-03-08 23:06 ` dpdklab
2024-03-08 23:06 ` dpdklab
2024-03-08 23:06 ` dpdklab
2024-03-08 23:07 ` dpdklab
2024-03-08 23:19 ` dpdklab
2024-03-08 23:20 ` dpdklab
2024-03-08 23:23 ` dpdklab
2024-03-08 23:26 ` dpdklab
2024-03-08 23:27 ` dpdklab
2024-03-08 23:27 ` dpdklab
2024-03-08 23:28 ` dpdklab
2024-03-08 23:28 ` dpdklab
2024-03-08 23:54 ` dpdklab
2024-03-08 23:56 ` dpdklab
2024-03-08 23:56 ` dpdklab
2024-03-08 23:58 ` dpdklab
2024-03-09  0:03 ` dpdklab
2024-03-09  0:03 ` dpdklab
2024-03-09  0:05 ` dpdklab
2024-03-09  0:05 ` dpdklab
2024-03-09  0:05 ` dpdklab
2024-03-09  0:05 ` dpdklab
2024-03-09  0:06 ` dpdklab
2024-03-09  0:06 ` dpdklab
2024-03-09  0:07 ` dpdklab
2024-03-09  0:07 ` dpdklab
2024-03-09  0:08 ` dpdklab
2024-03-09  0:10 ` dpdklab
2024-03-09  0:10 ` dpdklab
2024-03-09  0:10 ` dpdklab
2024-03-09  0:11 ` dpdklab
2024-03-09  0:11 ` dpdklab
2024-03-09  0:11 ` dpdklab
2024-03-09  0:11 ` dpdklab
2024-03-09  0:11 ` dpdklab
2024-03-09  0:12 ` dpdklab
2024-03-09  0:12 ` dpdklab
2024-03-09  0:12 ` dpdklab
2024-03-09  0:13 ` dpdklab
2024-03-09  0:14 ` dpdklab
2024-03-09  0:14 ` dpdklab
2024-03-09  0:14 ` dpdklab
2024-03-09  0:14 ` dpdklab
2024-03-09  0:15 ` dpdklab
2024-03-09  0:15 ` dpdklab
2024-03-09  0:15 ` dpdklab
2024-03-09  0:18 ` dpdklab
2024-03-09  0:18 ` dpdklab
2024-03-09  0:18 ` dpdklab
2024-03-09  0:20 ` dpdklab
2024-03-09  0:20 ` dpdklab
2024-03-09  0:23 ` dpdklab
2024-03-09  0:24 ` dpdklab
2024-03-09  0:50 ` dpdklab
2024-03-09  1:20 ` dpdklab
2024-03-09  1:41 ` dpdklab
2024-03-13 15:42 ` dpdklab
2024-03-13 17:47 ` dpdklab [this message]

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=65f1e6a0.020a0220.c3fb4.2892SMTPIN_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).