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| pw143596-143597 [PATCH] [v4,2/2] dts: add dynamic queue te
Date: Wed, 04 Sep 2024 17:18:20 -0700 (PDT)	[thread overview]
Message-ID: <66d8f8cc.810a0220.2fa7a3.9db1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240904154951.13524-3-jspewock@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Wednesday, September 04 2024 15:49:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143596-143597 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#178294

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


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

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-05  0:18 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240904154951.13524-3-jspewock@iol.unh.edu>
2024-09-04 15:32 ` |SUCCESS| pw143596-143597 [PATCH v4 2/2] dts: add dynamic queue test suite qemudev
2024-09-04 15:36 ` qemudev
2024-09-04 15:50 ` |SUCCESS| pw143597 " checkpatch
2024-09-04 16:44 ` 0-day Robot
2024-09-04 19:28 ` |SUCCESS| pw143596-143597 [PATCH] [v4,2/2] dts: add dynamic queue te dpdklab
2024-09-04 19:34 ` |PENDING| " dpdklab
2024-09-04 19:34 ` dpdklab
2024-09-04 19:35 ` dpdklab
2024-09-04 19:35 ` |SUCCESS| " dpdklab
2024-09-04 19:36 ` dpdklab
2024-09-04 19:36 ` dpdklab
2024-09-04 19:41 ` dpdklab
2024-09-04 20:15 ` dpdklab
2024-09-04 20:15 ` dpdklab
2024-09-04 21:53 ` dpdklab
2024-09-04 21:54 ` dpdklab
2024-09-04 21:54 ` dpdklab
2024-09-04 21:57 ` dpdklab
2024-09-04 21:57 ` dpdklab
2024-09-04 22:53 ` dpdklab
2024-09-04 23:03 ` dpdklab
2024-09-04 23:05 ` dpdklab
2024-09-04 23:22 ` dpdklab
2024-09-04 23:24 ` dpdklab
2024-09-04 23:26 ` dpdklab
2024-09-04 23:27 ` dpdklab
2024-09-04 23:28 ` dpdklab
2024-09-04 23:28 ` dpdklab
2024-09-04 23:30 ` dpdklab
2024-09-04 23:32 ` dpdklab
2024-09-04 23:38 ` dpdklab
2024-09-04 23:40 ` dpdklab
2024-09-04 23:41 ` dpdklab
2024-09-04 23:52 ` dpdklab
2024-09-05  0:18 ` dpdklab [this message]
2024-09-05  0:25 ` dpdklab
2024-09-05  0:25 ` dpdklab
2024-09-05  0:29 ` dpdklab
2024-09-05  0:30 ` dpdklab
2024-09-05  0:30 ` dpdklab
2024-09-05  0:30 ` dpdklab
2024-09-05  0:30 ` dpdklab
2024-09-05  0:31 ` dpdklab
2024-09-05  0:31 ` dpdklab
2024-09-05  0:32 ` dpdklab
2024-09-05  0:32 ` dpdklab
2024-09-05  0:33 ` dpdklab
2024-09-05  0:36 ` dpdklab
2024-09-05  0:38 ` dpdklab
2024-09-05  0:44 ` dpdklab
2024-09-05  0:44 ` dpdklab
2024-09-05  0:46 ` dpdklab
2024-09-05  0:46 ` dpdklab
2024-09-05  0:46 ` dpdklab
2024-09-05  0:48 ` dpdklab
2024-09-05  0:49 ` dpdklab
2024-09-05  0:49 ` dpdklab
2024-09-05  0:49 ` dpdklab
2024-09-05  0:51 ` dpdklab
2024-09-18  9:11 ` dpdklab
2024-09-18  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=66d8f8cc.810a0220.2fa7a3.9db1SMTPIN_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).