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| pw141312 [PATCH] test/event: increase default queue depth
Date: Wed, 19 Jun 2024 03:46:01 -0700 (PDT)	[thread overview]
Message-ID: <6672b6e9.050a0220.4d4a1.243fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240619063250.304825-1-anoobj@marvell.com>

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

_Functional Testing PASS_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, June 19 2024 06:32:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e50aa6011eb9133f2f1e49675dc6649e989126d6

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

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


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

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

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


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

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-19 10:46 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240619063250.304825-1-anoobj@marvell.com>
2024-06-19  6:05 ` |SUCCESS| pw141312 [PATCH] test/event: increase default queue depth for tests qemudev
2024-06-19  6:10 ` qemudev
2024-06-19  6:33 ` checkpatch
2024-06-19  7:24 ` 0-day Robot
2024-06-19 10:32 ` |SUCCESS| pw141312 [PATCH] test/event: increase default queue depth dpdklab
2024-06-19 10:38 ` dpdklab
2024-06-19 10:39 ` dpdklab
2024-06-19 10:39 ` dpdklab
2024-06-19 10:39 ` dpdklab
2024-06-19 10:40 ` dpdklab
2024-06-19 10:41 ` dpdklab
2024-06-19 10:43 ` dpdklab
2024-06-19 10:46 ` dpdklab [this message]
2024-06-19 10:52 ` dpdklab
2024-06-19 11:12 ` dpdklab
2024-06-19 11:25 ` dpdklab
2024-06-19 12:22 ` dpdklab
2024-06-19 12:26 ` dpdklab
2024-06-19 12:26 ` dpdklab
2024-06-19 12:26 ` dpdklab
2024-06-19 12:30 ` dpdklab
2024-06-19 12:32 ` dpdklab
2024-06-19 12:37 ` dpdklab
2024-06-19 12:57 ` dpdklab
2024-06-19 14:01 ` dpdklab
2024-06-19 14:03 ` dpdklab
2024-06-19 14:05 ` dpdklab
2024-06-19 14:05 ` dpdklab
2024-06-19 14:05 ` dpdklab
2024-06-19 14:06 ` dpdklab
2024-06-19 14:06 ` dpdklab
2024-06-19 14:08 ` dpdklab
2024-06-19 14:11 ` dpdklab
2024-06-19 14:13 ` dpdklab
2024-06-19 14:14 ` dpdklab
2024-06-19 14:16 ` dpdklab
2024-06-19 14:18 ` dpdklab
2024-06-19 14:18 ` dpdklab
2024-06-19 14:25 ` dpdklab
2024-06-19 14:28 ` dpdklab
2024-06-19 16:41 ` dpdklab
2024-06-19 16:43 ` dpdklab
2024-06-19 16:46 ` dpdklab
2024-06-19 16:53 ` dpdklab
2024-06-19 16:54 ` dpdklab
2024-06-19 16:55 ` dpdklab
2024-06-19 16:56 ` dpdklab
2024-06-19 16:57 ` dpdklab
2024-06-19 16:59 ` dpdklab
2024-06-19 17:00 ` dpdklab
2024-06-19 17:01 ` dpdklab
2024-06-19 17:02 ` dpdklab
2024-06-19 17:04 ` dpdklab
2024-06-19 17:07 ` dpdklab
2024-06-19 17:09 ` dpdklab
2024-06-19 17:14 ` dpdklab
2024-06-19 17:16 ` dpdklab
2024-06-19 17:16 ` dpdklab
2024-06-19 17:18 ` dpdklab
2024-06-19 17:23 ` dpdklab
2024-06-19 17:25 ` dpdklab
2024-06-19 17:26 ` dpdklab
2024-06-19 17:30 ` dpdklab
2024-06-19 17:32 ` dpdklab
2024-06-19 17:33 ` dpdklab
2024-06-19 17:37 ` dpdklab
2024-06-19 17:38 ` dpdklab
2024-06-19 17:38 ` dpdklab
2024-06-19 17:39 ` dpdklab
2024-06-19 17:40 ` dpdklab
2024-06-19 17:40 ` dpdklab
2024-06-19 17:44 ` dpdklab
2024-06-19 17:45 ` dpdklab
2024-06-19 17:45 ` dpdklab
2024-06-19 17:46 ` dpdklab
2024-06-19 17:46 ` dpdklab
2024-06-19 17:48 ` dpdklab
2024-06-19 17:49 ` dpdklab
2024-06-19 17:49 ` dpdklab
2024-06-19 17:53 ` dpdklab
2024-06-19 17:59 ` dpdklab
2024-06-19 18:11 ` dpdklab
2024-06-19 18:11 ` dpdklab
2024-06-19 18:12 ` dpdklab
2024-06-19 18:14 ` dpdklab
2024-06-19 18:15 ` dpdklab
2024-06-19 18:18 ` dpdklab
2024-06-19 18:21 ` dpdklab
2024-06-19 18:23 ` dpdklab
2024-06-19 18:28 ` dpdklab
2024-06-19 18:29 ` dpdklab
2024-06-19 18:30 ` dpdklab
2024-06-19 18:31 ` dpdklab
2024-06-19 18:32 ` dpdklab
2024-06-19 18:32 ` dpdklab
2024-06-19 18:33 ` dpdklab
2024-06-19 18:34 ` dpdklab
2024-06-19 18:35 ` dpdklab
2024-06-19 18:35 ` dpdklab
2024-06-19 18:37 ` dpdklab
2024-06-19 18:38 ` dpdklab
2024-06-19 18:39 ` dpdklab
2024-06-19 18:40 ` dpdklab
2024-06-19 18:41 ` dpdklab
2024-06-19 18:42 ` dpdklab
2024-06-19 18:52 ` dpdklab
2024-06-19 19:15 ` dpdklab
2024-06-19 20:02 ` dpdklab
2024-06-19 20:07 ` dpdklab
2024-06-19 22:28 ` dpdklab
2024-06-19 22:42 ` dpdklab
2024-06-21 17:00 ` 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=6672b6e9.050a0220.4d4a1.243fSMTPIN_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).