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| pw138796 [PATCH] doc: add tested AMD platforms
Date: Mon, 01 Apr 2024 15:45:48 -0700 (PDT)	[thread overview]
Message-ID: <660b391c.050a0220.ff40d.9de8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240326094654.2349537-1-ferruh.yigit@amd.com>

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

_Functional Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Tuesday, March 26 2024 09:46:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73

138796 --> functional testing pass

Test environment and result as below:

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-01 22:45 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240326094654.2349537-1-ferruh.yigit@amd.com>
2024-03-26  9:24 ` qemudev
2024-03-26  9:29 ` qemudev
2024-03-26  9:48 ` checkpatch
2024-03-26 10:24 ` dpdklab
2024-03-26 10:25 ` dpdklab
2024-03-26 10:26 ` dpdklab
2024-03-26 10:27 ` dpdklab
2024-03-26 10:27 ` dpdklab
2024-03-26 10:27 ` dpdklab
2024-03-26 10:28 ` dpdklab
2024-03-26 10:28 ` dpdklab
2024-03-26 10:29 ` dpdklab
2024-03-26 10:29 ` dpdklab
2024-03-26 10:30 ` dpdklab
2024-03-26 10:30 ` dpdklab
2024-03-26 10:31 ` dpdklab
2024-03-26 10:31 ` dpdklab
2024-03-26 10:32 ` dpdklab
2024-03-26 10:32 ` dpdklab
2024-03-26 10:32 ` dpdklab
2024-03-26 10:33 ` dpdklab
2024-03-26 10:33 ` dpdklab
2024-03-26 10:33 ` dpdklab
2024-03-26 10:33 ` dpdklab
2024-03-26 10:33 ` dpdklab
2024-03-26 10:34 ` dpdklab
2024-03-26 10:34 ` dpdklab
2024-03-26 10:34 ` dpdklab
2024-03-26 10:35 ` dpdklab
2024-03-26 10:35 ` dpdklab
2024-03-26 10:35 ` dpdklab
2024-03-26 10:35 ` dpdklab
2024-03-26 10:35 ` dpdklab
2024-03-26 10:36 ` dpdklab
2024-03-26 10:36 ` dpdklab
2024-03-26 10:36 ` dpdklab
2024-03-26 10:36 ` dpdklab
2024-03-26 10:36 ` dpdklab
2024-03-26 10:37 ` dpdklab
2024-03-26 10:37 ` dpdklab
2024-03-26 10:37 ` dpdklab
2024-03-26 10:38 ` dpdklab
2024-03-26 10:38 ` dpdklab
2024-03-26 10:39 ` dpdklab
2024-03-26 10:40 ` dpdklab
2024-03-26 10:41 ` dpdklab
2024-03-26 10:42 ` dpdklab
2024-03-26 10:42 ` dpdklab
2024-03-26 10:42 ` dpdklab
2024-03-26 10:43 ` dpdklab
2024-03-26 10:43 ` dpdklab
2024-03-26 10:43 ` dpdklab
2024-03-26 10:45 ` dpdklab
2024-03-26 10:46 ` dpdklab
2024-03-26 10:46 ` dpdklab
2024-03-26 10:47 ` dpdklab
2024-03-26 10:47 ` dpdklab
2024-03-26 10:47 ` dpdklab
2024-03-26 10:47 ` dpdklab
2024-03-26 10:47 ` dpdklab
2024-03-26 10:48 ` dpdklab
2024-03-26 10:49 ` dpdklab
2024-03-26 10:50 ` dpdklab
2024-03-26 10:50 ` dpdklab
2024-03-26 10:51 ` dpdklab
2024-03-26 10:51 ` dpdklab
2024-03-26 10:51 ` dpdklab
2024-03-26 10:52 ` dpdklab
2024-03-26 10:54 ` dpdklab
2024-03-26 11:27 ` dpdklab
2024-03-26 13:14 ` dpdklab
2024-04-01 22:38 ` dpdklab
2024-04-01 22:41 ` dpdklab
2024-04-01 22:45 ` dpdklab [this message]
2024-04-01 22:49 ` dpdklab
2024-04-01 23:09 ` 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=660b391c.050a0220.ff40d.9de8SMTPIN_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).