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| pw142761 [PATCH] [v3] doc: announce changes to dma device
Date: Tue, 30 Jul 2024 10:06:31 -0700 (PDT)	[thread overview]
Message-ID: <66a91d97.4a0a0220.b3d3c.7ffcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240730125302.2132377-1-amitprakashs@marvell.com>

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

_Functional Testing PASS_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Tuesday, July 30 2024 12:53:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4b5abe7ec1ed2d43a285599bbba23f62ac049d8f

142761 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#171690

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

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-30 17:13 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240730125302.2132377-1-amitprakashs@marvell.com>
2024-07-30 13:42 ` |SUCCESS| pw142761 [PATCH v3] doc: announce changes to dma device structures qemudev
2024-07-30 13:46 ` qemudev
2024-07-30 14:07 ` |WARNING| " checkpatch
2024-07-30 15:02 ` |SUCCESS| " 0-day Robot
2024-07-30 16:32 ` |SUCCESS| pw142761 [PATCH] [v3] doc: announce changes to dma device dpdklab
2024-07-30 16:33 ` |PENDING| " dpdklab
2024-07-30 16:35 ` |SUCCESS| " dpdklab
2024-07-30 16:37 ` dpdklab
2024-07-30 16:40 ` dpdklab
2024-07-30 16:41 ` dpdklab
2024-07-30 16:41 ` dpdklab
2024-07-30 16:50 ` dpdklab
2024-07-30 16:53 ` dpdklab
2024-07-30 16:54 ` dpdklab
2024-07-30 16:54 ` dpdklab
2024-07-30 16:55 ` |PENDING| " dpdklab
2024-07-30 16:57 ` |SUCCESS| " dpdklab
2024-07-30 17:01 ` dpdklab
2024-07-30 17:02 ` dpdklab
2024-07-30 17:02 ` |PENDING| " dpdklab
2024-07-30 17:06 ` dpdklab [this message]
2024-07-30 17:15 ` dpdklab
2024-07-30 17:16 ` dpdklab
2024-07-30 17:16 ` |SUCCESS| " dpdklab
2024-07-30 17:16 ` |PENDING| " dpdklab
2024-07-30 17:21 ` dpdklab
2024-07-30 17:22 ` dpdklab
2024-07-30 17:22 ` dpdklab
2024-07-30 17:26 ` |SUCCESS| " dpdklab
2024-07-30 17:26 ` |PENDING| " dpdklab
2024-07-30 17:27 ` dpdklab
2024-07-30 17:27 ` dpdklab
2024-07-30 17:32 ` dpdklab
2024-07-30 17:33 ` dpdklab
2024-07-30 17:41 ` |SUCCESS| " dpdklab
2024-07-30 17:42 ` dpdklab
2024-07-30 18:13 ` |PENDING| " dpdklab
2024-07-30 18:13 ` dpdklab
2024-07-30 18:14 ` dpdklab
2024-07-30 18:15 ` dpdklab
2024-07-30 18:18 ` |SUCCESS| " dpdklab
2024-07-30 18:18 ` dpdklab
2024-07-30 18:19 ` dpdklab
2024-07-30 18:23 ` |PENDING| " dpdklab
2024-07-30 18:25 ` dpdklab
2024-07-30 18:25 ` dpdklab
2024-07-30 18:28 ` dpdklab
2024-07-30 18:32 ` dpdklab
2024-07-30 18:36 ` dpdklab
2024-07-30 18:43 ` dpdklab
2024-07-30 18:46 ` dpdklab
2024-07-30 18:48 ` dpdklab
2024-07-30 18:50 ` dpdklab
2024-07-30 18:55 ` dpdklab
2024-07-30 18:55 ` dpdklab
2024-07-30 18:57 ` dpdklab
2024-07-30 18:57 ` dpdklab
2024-07-30 18:57 ` dpdklab
2024-07-30 18:58 ` dpdklab
2024-07-30 19:00 ` dpdklab
2024-07-30 19:02 ` dpdklab
2024-07-30 19:07 ` dpdklab
2024-07-30 19:36 ` dpdklab
2024-07-30 19:38 ` dpdklab
2024-07-30 19:43 ` dpdklab
2024-07-30 19:44 ` dpdklab
2024-07-30 19:44 ` dpdklab
2024-07-30 19:45 ` dpdklab
2024-07-30 19:45 ` dpdklab
2024-07-30 19:46 ` dpdklab
2024-07-30 19:47 ` dpdklab
2024-07-30 19:51 ` dpdklab
2024-07-30 19:52 ` dpdklab
2024-07-30 19:57 ` dpdklab
2024-07-30 19:57 ` dpdklab
2024-07-30 20:01 ` dpdklab
2024-07-30 20:01 ` dpdklab
2024-07-30 20:03 ` dpdklab
2024-07-30 20:06 ` dpdklab
2024-07-30 20:11 ` dpdklab
2024-07-30 20:13 ` dpdklab
2024-07-30 20:14 ` dpdklab
2024-07-30 20:15 ` dpdklab
2024-07-30 20:16 ` dpdklab
2024-07-30 20:18 ` dpdklab
2024-07-30 20:18 ` dpdklab
2024-07-30 20:19 ` dpdklab
2024-07-30 20:19 ` dpdklab
2024-07-30 20:22 ` dpdklab
2024-07-30 20:23 ` dpdklab
2024-07-30 20:28 ` dpdklab
2024-07-30 20:28 ` dpdklab
2024-07-30 20:30 ` dpdklab
2024-07-30 20:30 ` dpdklab
2024-07-30 20:33 ` dpdklab
2024-07-30 20:33 ` dpdklab
2024-07-30 20:33 ` dpdklab
2024-07-30 20:34 ` dpdklab
2024-07-30 20:35 ` dpdklab
2024-07-30 20:37 ` dpdklab
2024-07-30 20:37 ` dpdklab
2024-07-30 20:40 ` dpdklab
2024-07-30 20:40 ` dpdklab
2024-07-30 20:44 ` dpdklab
2024-07-30 20:47 ` |SUCCESS| " dpdklab
2024-07-30 20:48 ` |PENDING| " dpdklab
2024-07-30 20:49 ` dpdklab
2024-07-30 20:50 ` dpdklab
2024-07-30 20:51 ` |SUCCESS| " dpdklab
2024-07-30 20:58 ` |PENDING| " dpdklab
2024-07-30 21:07 ` dpdklab
2024-07-30 21:07 ` dpdklab
2024-07-30 21:20 ` |SUCCESS| " dpdklab
2024-07-30 21:23 ` dpdklab
2024-07-31  1:08 ` 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=66a91d97.4a0a0220.b3d3c.7ffcSMTPIN_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).