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| pw138471 [PATCH] [v2] doc: add dma perf feature details
Date: Mon, 18 Mar 2024 16:17:17 -0700 (PDT)	[thread overview]
Message-ID: <65f8cb7d.050a0220.39849.528bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240318184553.2770394-1-amitprakashs@marvell.com>

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

_Functional Testing PASS_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Monday, March 18 2024 18:45:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138471 --> 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/29588/

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-18 23:17 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240318184553.2770394-1-amitprakashs@marvell.com>
2024-03-18 18:35 ` |SUCCESS| pw138471 [PATCH v2] " qemudev
2024-03-18 18:40 ` qemudev
2024-03-18 18:46 ` checkpatch
2024-03-18 19:43 ` 0-day Robot
2024-03-18 23:08 ` |SUCCESS| pw138471 [PATCH] [v2] " dpdklab
2024-03-18 23:09 ` dpdklab
2024-03-18 23:17 ` dpdklab [this message]
2024-03-18 23:19 ` dpdklab
2024-03-18 23:23 ` dpdklab
2024-03-18 23:24 ` dpdklab
2024-03-18 23:25 ` dpdklab
2024-03-18 23:25 ` dpdklab
2024-03-18 23:25 ` dpdklab
2024-03-18 23:25 ` dpdklab
2024-03-18 23:25 ` dpdklab
2024-03-18 23:26 ` dpdklab
2024-03-18 23:26 ` dpdklab
2024-03-18 23:26 ` dpdklab
2024-03-18 23:26 ` dpdklab
2024-03-18 23:26 ` dpdklab
2024-03-18 23:26 ` dpdklab
2024-03-18 23:27 ` dpdklab
2024-03-18 23:27 ` dpdklab
2024-03-18 23:27 ` dpdklab
2024-03-18 23:27 ` dpdklab
2024-03-18 23:27 ` dpdklab
2024-03-18 23:28 ` dpdklab
2024-03-18 23:28 ` dpdklab
2024-03-18 23:28 ` dpdklab
2024-03-18 23:28 ` dpdklab
2024-03-18 23:28 ` dpdklab
2024-03-18 23:28 ` dpdklab
2024-03-18 23:28 ` dpdklab
2024-03-18 23:29 ` dpdklab
2024-03-18 23:29 ` dpdklab
2024-03-18 23:29 ` dpdklab
2024-03-18 23:29 ` dpdklab
2024-03-18 23:29 ` dpdklab
2024-03-18 23:29 ` dpdklab
2024-03-18 23:29 ` dpdklab
2024-03-18 23:30 ` dpdklab
2024-03-18 23:30 ` dpdklab
2024-03-18 23:30 ` dpdklab
2024-03-18 23:30 ` dpdklab
2024-03-18 23:30 ` dpdklab
2024-03-18 23:30 ` dpdklab
2024-03-18 23:30 ` dpdklab
2024-03-18 23:31 ` dpdklab
2024-03-18 23:31 ` dpdklab
2024-03-18 23:31 ` dpdklab
2024-03-18 23:32 ` dpdklab
2024-03-18 23:32 ` dpdklab
2024-03-18 23:32 ` dpdklab
2024-03-18 23:32 ` dpdklab
2024-03-18 23:32 ` dpdklab
2024-03-18 23:32 ` dpdklab
2024-03-18 23:32 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:33 ` dpdklab
2024-03-18 23:34 ` dpdklab
2024-03-18 23:34 ` dpdklab
2024-03-18 23:34 ` dpdklab
2024-03-18 23:35 ` dpdklab
2024-03-18 23:36 ` dpdklab
2024-03-18 23:36 ` dpdklab
2024-03-18 23:36 ` dpdklab
2024-03-18 23:38 ` dpdklab
2024-03-18 23:39 ` dpdklab
2024-03-18 23:46 ` dpdklab
2024-03-18 23:58 ` dpdklab
2024-03-19  0:26 ` dpdklab
2024-03-19  0:42 ` dpdklab
2024-03-20 22:27 ` dpdklab
2024-03-20 23:26 ` 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=65f8cb7d.050a0220.39849.528bSMTPIN_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).