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| pw138080 [PATCH] config/arm: sort in alphabetical order
Date: Thu, 07 Mar 2024 18:54:35 -0800 (PST)	[thread overview]
Message-ID: <65ea7deb.0d0a0220.7d2a2.505dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240307060210.114-1-anoobj@marvell.com>

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

_Functional Testing PASS_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Thursday, March 07 2024 06:02:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a454f84f715608ee709a4c6ba00edf2e4b62b69

138080 --> 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/29450/

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-08  2:54 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240307060210.114-1-anoobj@marvell.com>
2024-03-07  5:39 ` qemudev
2024-03-07  5:43 ` qemudev
2024-03-07  6:02 ` checkpatch
2024-03-07  6:50 ` dpdklab
2024-03-07  6:51 ` dpdklab
2024-03-07  6:52 ` dpdklab
2024-03-07  6:52 ` dpdklab
2024-03-07  6:53 ` dpdklab
2024-03-07  6:53 ` dpdklab
2024-03-07  6:55 ` dpdklab
2024-03-07  6:58 ` dpdklab
2024-03-07  6:59 ` dpdklab
2024-03-07  6:59 ` dpdklab
2024-03-07  6:59 ` dpdklab
2024-03-07  7:02 ` dpdklab
2024-03-07  7:04 ` 0-day Robot
2024-03-07  7:04 ` dpdklab
2024-03-07  7:05 ` dpdklab
2024-03-07  7:05 ` dpdklab
2024-03-07  7:06 ` dpdklab
2024-03-07  7:07 ` dpdklab
2024-03-07  7:13 ` dpdklab
2024-03-07  7:14 ` dpdklab
2024-03-07  7:15 ` dpdklab
2024-03-07  7:35 ` dpdklab
2024-03-07  7:35 ` dpdklab
2024-03-07  7:38 ` dpdklab
2024-03-07  7:38 ` dpdklab
2024-03-07  7:39 ` dpdklab
2024-03-07  7:40 ` dpdklab
2024-03-07  7:45 ` dpdklab
2024-03-07  8:05 ` dpdklab
2024-03-07  8:11 ` dpdklab
2024-03-07  8:13 ` dpdklab
2024-03-07  8:27 ` dpdklab
2024-03-07  8:27 ` dpdklab
2024-03-07  8:27 ` dpdklab
2024-03-07  8:28 ` dpdklab
2024-03-07  8:28 ` dpdklab
2024-03-07  8:29 ` dpdklab
2024-03-07  8:30 ` dpdklab
2024-03-07  8:30 ` dpdklab
2024-03-07  8:31 ` dpdklab
2024-03-07  8:32 ` dpdklab
2024-03-07  8:33 ` dpdklab
2024-03-07  8:34 ` dpdklab
2024-03-07  8:35 ` dpdklab
2024-03-07  8:36 ` dpdklab
2024-03-07  8:37 ` dpdklab
2024-03-07  8:38 ` dpdklab
2024-03-07  8:38 ` dpdklab
2024-03-07  8:40 ` dpdklab
2024-03-07  8:40 ` dpdklab
2024-03-07  8:41 ` dpdklab
2024-03-07  8:41 ` dpdklab
2024-03-07  8:42 ` dpdklab
2024-03-07  8:42 ` dpdklab
2024-03-07  8:45 ` dpdklab
2024-03-07  8:47 ` dpdklab
2024-03-07  8:48 ` dpdklab
2024-03-07  8:50 ` dpdklab
2024-03-07  8:52 ` dpdklab
2024-03-07  9:02 ` dpdklab
2024-03-07  9:07 ` dpdklab
2024-03-07  9:08 ` dpdklab
2024-03-07  9:24 ` dpdklab
2024-03-07 10:52 ` dpdklab
2024-03-07 11:24 ` dpdklab
2024-03-08  2:42 ` dpdklab
2024-03-08  2:46 ` dpdklab
2024-03-08  2:50 ` dpdklab
2024-03-08  2:54 ` dpdklab [this message]
2024-03-11  6:55 ` dpdklab
2024-03-11  7:32 ` dpdklab
2024-03-11  8:31 ` 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=65ea7deb.0d0a0220.7d2a2.505dSMTPIN_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).