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| pw137193 [PATCH] [v2,1/1] net/octeon_ep: use devarg to ena
Date: Tue, 27 Feb 2024 15:13:23 -0800 (PST)	[thread overview]
Message-ID: <65de6c93.050a0220.cb8ca.f098SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240226085945.1401546-1-vattunuru@marvell.com>

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

_Functional Testing PASS_

Submitter: Vamsi Attunuru <vattunuru@marvell.com>
Date: Monday, February 26 2024 08:59:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ab5b7cd5a0b563e6d49be6c8beaad1f39c581a5c

137193 --> functional testing pass

Test environment and result as below:

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


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/29257/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-27 23:13 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240226085945.1401546-1-vattunuru@marvell.com>
2024-02-26  8:37 ` |SUCCESS| pw137193 [PATCH v2 1/1] net/octeon_ep: use devarg to enable ISM accesses qemudev
2024-02-26  8:41 ` qemudev
2024-02-26  9:00 ` checkpatch
2024-02-26 10:04 ` 0-day Robot
2024-02-27 22:57 ` |SUCCESS| pw137193 [PATCH] [v2,1/1] net/octeon_ep: use devarg to ena dpdklab
2024-02-27 22:59 ` dpdklab
2024-02-27 23:04 ` dpdklab
2024-02-27 23:13 ` dpdklab [this message]
2024-02-26 11:24 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26 11:21 dpdklab
2024-02-26 11:06 dpdklab
2024-02-26 10:44 dpdklab
2024-02-26 10:34 dpdklab
2024-02-26 10:32 dpdklab
2024-02-26 10:31 dpdklab
2024-02-26 10:29 dpdklab
2024-02-26 10:28 dpdklab
2024-02-26 10:28 dpdklab
2024-02-26 10:26 dpdklab
2024-02-26 10:26 dpdklab
2024-02-26 10:25 dpdklab
2024-02-26 10:09 dpdklab
2024-02-26 10:09 dpdklab
2024-02-26 10:09 dpdklab
2024-02-26 10:08 dpdklab
2024-02-26 10:07 dpdklab
2024-02-26 10:07 dpdklab
2024-02-26 10:07 dpdklab
2024-02-26 10:06 dpdklab
2024-02-26 10:06 dpdklab
2024-02-26 10:06 dpdklab
2024-02-26 10:06 dpdklab
2024-02-26 10:06 dpdklab
2024-02-26 10:06 dpdklab
2024-02-26 10:05 dpdklab
2024-02-26 10:05 dpdklab
2024-02-26 10:05 dpdklab
2024-02-26 10:05 dpdklab
2024-02-26 10:05 dpdklab
2024-02-26 10:04 dpdklab
2024-02-26 10:04 dpdklab
2024-02-26 10:04 dpdklab
2024-02-26 10:04 dpdklab
2024-02-26 10:03 dpdklab
2024-02-26 10:03 dpdklab
2024-02-26 10:03 dpdklab
2024-02-26 10:00 dpdklab
2024-02-26 10:00 dpdklab
2024-02-26 10:00 dpdklab
2024-02-26 10:00 dpdklab
2024-02-26 10:00 dpdklab
2024-02-26  9:59 dpdklab
2024-02-26  9:59 dpdklab
2024-02-26  9:59 dpdklab
2024-02-26  9:59 dpdklab
2024-02-26  9:59 dpdklab
2024-02-26  9:59 dpdklab
2024-02-26  9:59 dpdklab
2024-02-26  9:58 dpdklab
2024-02-26  9:58 dpdklab
2024-02-26  9:58 dpdklab
2024-02-26  9:58 dpdklab
2024-02-26  9:58 dpdklab
2024-02-26  9:57 dpdklab
2024-02-26  9:57 dpdklab
2024-02-26  9:57 dpdklab
2024-02-26  9:57 dpdklab
2024-02-26  9:57 dpdklab
2024-02-26  9:56 dpdklab
2024-02-26  9:56 dpdklab
2024-02-26  9:56 dpdklab
2024-02-26  9:55 dpdklab
2024-02-26  9:51 dpdklab
2024-02-26  9:51 dpdklab
2024-02-26  9:50 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=65de6c93.050a0220.cb8ca.f098SMTPIN_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).