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| pw138159-138165 [PATCH] [v9,7/7] dts: add pmd_buffer_scatt
Date: Thu, 14 Mar 2024 20:50:10 -0700 (PDT)	[thread overview]
Message-ID: <65f3c572.b00a0220.262cd.794fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240311154405.13269-8-jspewock@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Monday, March 11 2024 15:44:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138159-138165 --> functional testing pass

Test environment and result as below:

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


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


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


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29502/

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-15  3:50 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240311154405.13269-8-jspewock@iol.unh.edu>
2024-03-11 15:25 ` |SUCCESS| pw138159-138165 [PATCH v9 7/7] dts: add pmd_buffer_scatter test suite qemudev
2024-03-11 15:29 ` qemudev
2024-03-11 15:47 ` |SUCCESS| pw138165 " checkpatch
2024-03-11 16:42 ` 0-day Robot
2024-03-11 17:53 ` |SUCCESS| pw138159-138165 [PATCH] [v9,7/7] dts: add pmd_buffer_scatt dpdklab
2024-03-11 17:55 ` dpdklab
2024-03-11 17:56 ` dpdklab
2024-03-11 17:56 ` dpdklab
2024-03-11 18:16 ` dpdklab
2024-03-11 18:23 ` dpdklab
2024-03-11 18:37 ` dpdklab
2024-03-11 18:37 ` dpdklab
2024-03-11 18:38 ` dpdklab
2024-03-11 18:39 ` dpdklab
2024-03-11 18:39 ` dpdklab
2024-03-11 18:40 ` dpdklab
2024-03-11 18:41 ` dpdklab
2024-03-11 18:41 ` dpdklab
2024-03-11 18:42 ` dpdklab
2024-03-11 18:42 ` dpdklab
2024-03-11 18:43 ` dpdklab
2024-03-11 18:43 ` dpdklab
2024-03-11 18:43 ` dpdklab
2024-03-11 18:44 ` dpdklab
2024-03-11 18:44 ` dpdklab
2024-03-11 18:44 ` dpdklab
2024-03-11 18:44 ` dpdklab
2024-03-11 18:44 ` dpdklab
2024-03-11 18:45 ` dpdklab
2024-03-11 18:45 ` dpdklab
2024-03-11 18:46 ` dpdklab
2024-03-11 18:46 ` dpdklab
2024-03-11 18:46 ` dpdklab
2024-03-11 18:46 ` dpdklab
2024-03-11 18:46 ` dpdklab
2024-03-11 18:46 ` dpdklab
2024-03-11 18:46 ` dpdklab
2024-03-11 18:47 ` dpdklab
2024-03-11 18:47 ` dpdklab
2024-03-11 18:47 ` dpdklab
2024-03-11 18:47 ` dpdklab
2024-03-11 18:48 ` dpdklab
2024-03-11 18:48 ` dpdklab
2024-03-11 18:48 ` dpdklab
2024-03-11 18:49 ` dpdklab
2024-03-11 18:49 ` dpdklab
2024-03-11 18:49 ` dpdklab
2024-03-11 18:49 ` dpdklab
2024-03-11 18:49 ` dpdklab
2024-03-11 18:50 ` dpdklab
2024-03-11 18:50 ` dpdklab
2024-03-11 18:51 ` dpdklab
2024-03-11 18:51 ` dpdklab
2024-03-11 18:52 ` dpdklab
2024-03-11 18:52 ` dpdklab
2024-03-11 18:52 ` dpdklab
2024-03-11 18:53 ` dpdklab
2024-03-11 18:53 ` dpdklab
2024-03-11 18:53 ` dpdklab
2024-03-11 18:54 ` dpdklab
2024-03-11 18:54 ` dpdklab
2024-03-11 18:54 ` dpdklab
2024-03-11 18:54 ` dpdklab
2024-03-11 18:54 ` dpdklab
2024-03-11 18:54 ` dpdklab
2024-03-11 18:54 ` dpdklab
2024-03-11 18:55 ` dpdklab
2024-03-11 18:57 ` dpdklab
2024-03-11 19:24 ` dpdklab
2024-03-11 21:08 ` dpdklab
2024-03-11 23:21 ` dpdklab
2024-03-11 23:25 ` dpdklab
2024-03-11 23:29 ` dpdklab
2024-03-11 23:33 ` dpdklab
2024-03-15  3:05 ` dpdklab
2024-03-15  3:50 ` 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=65f3c572.b00a0220.262cd.794fSMTPIN_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).