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| pw138465 [PATCH] doc: add dma perf feature details
Date: Wed, 20 Mar 2024 10:39:25 -0700 (PDT)	[thread overview]
Message-ID: <65fb1f4d.050a0220.5f946.abf2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240318181730.2725829-1-amitprakashs@marvell.com>

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

_Functional Testing PASS_

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

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


Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 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/29586/

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-20 17:39 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240318181730.2725829-1-amitprakashs@marvell.com>
2024-03-18 17:55 ` |WARNING| " qemudev
2024-03-18 18:18 ` |SUCCESS| " checkpatch
2024-03-18 19:08 ` dpdklab
2024-03-18 19:09 ` dpdklab
2024-03-18 19:09 ` dpdklab
2024-03-18 19:10 ` dpdklab
2024-03-18 19:11 ` dpdklab
2024-03-18 19:16 ` dpdklab
2024-03-18 19:16 ` dpdklab
2024-03-18 19:16 ` dpdklab
2024-03-18 19:16 ` dpdklab
2024-03-18 19:17 ` dpdklab
2024-03-18 19:17 ` dpdklab
2024-03-18 19:17 ` dpdklab
2024-03-18 19:17 ` dpdklab
2024-03-18 19:18 ` dpdklab
2024-03-18 19:18 ` dpdklab
2024-03-18 19:18 ` dpdklab
2024-03-18 19:18 ` dpdklab
2024-03-18 19:19 ` dpdklab
2024-03-18 19:19 ` dpdklab
2024-03-18 19:19 ` dpdklab
2024-03-18 19:19 ` dpdklab
2024-03-18 19:20 ` dpdklab
2024-03-18 19:20 ` dpdklab
2024-03-18 19:20 ` dpdklab
2024-03-18 19:22 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:23 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:24 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:25 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:26 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:28 ` dpdklab
2024-03-18 19:29 ` dpdklab
2024-03-18 19:29 ` dpdklab
2024-03-18 19:29 ` dpdklab
2024-03-18 19:29 ` dpdklab
2024-03-18 19:30 ` dpdklab
2024-03-18 19:32 ` dpdklab
2024-03-18 19:32 ` dpdklab
2024-03-18 19:32 ` dpdklab
2024-03-18 19:32 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:34 ` dpdklab
2024-03-18 19:36 ` dpdklab
2024-03-18 19:38 ` dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-20 17:05 ` dpdklab
2024-03-20 17:39 ` 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=65fb1f4d.050a0220.5f946.abf2SMTPIN_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).