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| pw141971-141973 [PATCH] [v4,3/3] dts: queue suite conf sch
Date: Fri, 28 Jun 2024 10:24:38 -0700 (PDT)	[thread overview]
Message-ID: <667ef1d6.170a0220.b2ff6.46caSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240628161930.15915-3-dmarx@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Friday, June 28 2024 16:19:30 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b

141971-141973 --> functional testing pass

Test environment and result as below:

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: Unknown

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-28 17:25 UTC|newest]

Thread overview: 118+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240628161930.15915-3-dmarx@iol.unh.edu>
2024-06-28 15:55 ` |SUCCESS| pw141971-141973 [PATCH v4 3/3] dts: queue suite conf schema qemudev
2024-06-28 16:00 ` qemudev
2024-06-28 16:21 ` |SUCCESS| pw141973 " checkpatch
2024-06-28 17:14 ` |PENDING| pw141971-141973 [PATCH] [v4,3/3] dts: queue suite conf sch dpdklab
2024-06-28 17:22 ` dpdklab
2024-06-28 17:24 ` |SUCCESS| " dpdklab
2024-06-28 17:24 ` dpdklab
2024-06-28 17:24 ` |PENDING| " dpdklab
2024-06-28 17:24 ` |SUCCESS| " dpdklab
2024-06-28 17:24 ` dpdklab
2024-06-28 17:24 ` dpdklab [this message]
2024-06-28 17:25 ` |SUCCESS| pw141973 [PATCH v4 3/3] dts: queue suite conf schema 0-day Robot
2024-06-28 17:25 ` |SUCCESS| pw141971-141973 [PATCH] [v4,3/3] dts: queue suite conf sch dpdklab
2024-06-28 17:25 ` |PENDING| " dpdklab
2024-06-28 17:26 ` dpdklab
2024-06-28 17:26 ` dpdklab
2024-06-28 17:26 ` |SUCCESS| " dpdklab
2024-06-28 17:28 ` dpdklab
2024-06-28 17:33 ` dpdklab
2024-06-28 17:36 ` dpdklab
2024-06-28 17:37 ` dpdklab
2024-06-28 17:43 ` |PENDING| " dpdklab
2024-06-28 17:48 ` |SUCCESS| " dpdklab
2024-06-28 17:48 ` dpdklab
2024-06-28 17:48 ` |PENDING| " dpdklab
2024-06-28 17:48 ` dpdklab
2024-06-28 17:49 ` dpdklab
2024-06-28 17:51 ` dpdklab
2024-06-28 17:52 ` dpdklab
2024-06-28 17:53 ` dpdklab
2024-06-28 17:59 ` dpdklab
2024-06-28 18:02 ` |SUCCESS| " dpdklab
2024-06-28 18:02 ` |PENDING| " dpdklab
2024-06-28 18:03 ` dpdklab
2024-06-28 18:03 ` dpdklab
2024-06-28 18:10 ` dpdklab
2024-06-28 18:11 ` dpdklab
2024-06-28 18:13 ` |SUCCESS| " dpdklab
2024-06-28 18:13 ` |PENDING| " dpdklab
2024-06-28 18:14 ` dpdklab
2024-06-28 18:15 ` dpdklab
2024-06-28 18:17 ` dpdklab
2024-06-28 18:18 ` dpdklab
2024-06-28 18:18 ` dpdklab
2024-06-28 18:19 ` dpdklab
2024-06-28 18:19 ` dpdklab
2024-06-28 18:21 ` dpdklab
2024-06-28 18:22 ` dpdklab
2024-06-28 18:22 ` dpdklab
2024-06-28 18:22 ` dpdklab
2024-06-28 18:23 ` dpdklab
2024-06-28 18:26 ` dpdklab
2024-06-28 18:27 ` dpdklab
2024-06-28 18:29 ` dpdklab
2024-06-28 18:29 ` dpdklab
2024-06-28 18:29 ` dpdklab
2024-06-28 18:30 ` dpdklab
2024-06-28 18:31 ` dpdklab
2024-06-28 18:31 ` dpdklab
2024-06-28 18:35 ` dpdklab
2024-06-28 18:36 ` dpdklab
2024-06-28 18:36 ` dpdklab
2024-06-28 18:36 ` dpdklab
2024-06-28 18:37 ` dpdklab
2024-06-28 18:37 ` dpdklab
2024-06-28 18:39 ` dpdklab
2024-06-28 18:42 ` dpdklab
2024-06-28 18:43 ` dpdklab
2024-06-28 18:43 ` dpdklab
2024-06-28 18:44 ` dpdklab
2024-06-28 18:46 ` dpdklab
2024-06-28 18:46 ` dpdklab
2024-06-28 18:46 ` dpdklab
2024-06-28 18:50 ` dpdklab
2024-06-28 18:52 ` dpdklab
2024-06-28 18:52 ` dpdklab
2024-06-28 18:52 ` dpdklab
2024-06-28 18:54 ` dpdklab
2024-06-28 18:55 ` dpdklab
2024-06-28 18:56 ` dpdklab
2024-06-28 18:58 ` dpdklab
2024-06-28 19:00 ` dpdklab
2024-06-28 19:01 ` dpdklab
2024-06-28 19:05 ` dpdklab
2024-06-28 19:05 ` dpdklab
2024-06-28 19:07 ` dpdklab
2024-06-28 19:08 ` dpdklab
2024-06-28 19:09 ` dpdklab
2024-06-28 19:11 ` dpdklab
2024-06-28 19:11 ` dpdklab
2024-06-28 19:11 ` dpdklab
2024-06-28 19:12 ` dpdklab
2024-06-28 19:13 ` dpdklab
2024-06-28 19:13 ` dpdklab
2024-06-28 19:15 ` dpdklab
2024-06-28 19:16 ` dpdklab
2024-06-28 19:18 ` |SUCCESS| " dpdklab
2024-06-28 19:18 ` |PENDING| " dpdklab
2024-06-28 19:18 ` dpdklab
2024-06-28 19:19 ` dpdklab
2024-06-28 19:20 ` dpdklab
2024-06-28 19:20 ` dpdklab
2024-06-28 19:24 ` |SUCCESS| " dpdklab
2024-06-28 19:25 ` |PENDING| " dpdklab
2024-06-28 19:27 ` dpdklab
2024-06-28 19:32 ` dpdklab
2024-06-28 19:40 ` dpdklab
2024-06-28 19:43 ` |SUCCESS| " dpdklab
2024-06-28 19:43 ` dpdklab
2024-06-28 19:44 ` |PENDING| " dpdklab
2024-06-28 19:48 ` dpdklab
2024-06-28 19:53 ` |SUCCESS| " dpdklab
2024-06-28 22:44 ` dpdklab
2024-06-28 22:52 ` |PENDING| " dpdklab
2024-06-28 22:54 ` |SUCCESS| " dpdklab
2024-06-29  1:52 ` dpdklab
2024-06-29  2:05 ` dpdklab
2024-06-29 12:24 ` 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=667ef1d6.170a0220.b2ff6.46caSMTPIN_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).