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| pw143300-143302 [PATCH] [v1,3/3] test/crypto: add support
Date: Thu, 22 Aug 2024 05:00:02 -0700 (PDT)	[thread overview]
Message-ID: <66c72842.170a0220.1a80c4.4af7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240822102856.3965710-3-vvelumuri@marvell.com>

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

_Functional Testing PASS_

Submitter: Vidya Sagar Velumuri <vvelumuri@marvell.com>
Date: Thursday, August 22 2024 10:28:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

143300-143302 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#176332

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  |
+------------+--------+


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  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-22 12:00 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240822102856.3965710-3-vvelumuri@marvell.com>
2024-08-22 10:03 ` |SUCCESS| pw143300-143302 [PATCH v1 3/3] test/crypto: add support for error recovery qemudev
2024-08-22 10:07 ` qemudev
2024-08-22 10:30 ` |SUCCESS| pw143302 " checkpatch
2024-08-22 11:23 ` 0-day Robot
2024-08-22 11:36 ` |SUCCESS| pw143300-143302 [PATCH] [v1,3/3] test/crypto: add support dpdklab
2024-08-22 11:48 ` dpdklab
2024-08-22 11:52 ` dpdklab
2024-08-22 11:53 ` dpdklab
2024-08-22 11:53 ` dpdklab
2024-08-22 12:00 ` dpdklab [this message]
2024-08-22 12:00 ` dpdklab
2024-08-22 12:01 ` dpdklab
2024-08-22 12:01 ` dpdklab
2024-08-22 12:02 ` dpdklab
2024-08-22 12:02 ` dpdklab
2024-08-22 12:03 ` dpdklab
2024-08-22 12:04 ` dpdklab
2024-08-22 12:06 ` dpdklab
2024-08-22 12:06 ` dpdklab
2024-08-22 12:06 ` dpdklab
2024-08-22 12:07 ` dpdklab
2024-08-22 12:08 ` dpdklab
2024-08-22 12:08 ` dpdklab
2024-08-22 12:09 ` dpdklab
2024-08-22 12:09 ` dpdklab
2024-08-22 12:14 ` |PENDING| " dpdklab
2024-08-22 12:16 ` |SUCCESS| " dpdklab
2024-08-22 12:17 ` dpdklab
2024-08-22 12:20 ` dpdklab
2024-08-22 12:21 ` dpdklab
2024-08-22 12:21 ` dpdklab
2024-08-22 12:23 ` dpdklab
2024-08-22 12:43 ` |PENDING| " dpdklab
2024-08-22 12:58 ` |SUCCESS| " dpdklab
2024-08-22 13:00 ` dpdklab
2024-08-22 13:01 ` dpdklab
2024-08-22 13:03 ` dpdklab
2024-08-22 13:04 ` dpdklab
2024-08-22 13:05 ` dpdklab
2024-08-22 13:05 ` dpdklab
2024-08-22 13:06 ` dpdklab
2024-08-22 13:06 ` dpdklab
2024-08-22 13:17 ` |PENDING| " dpdklab
2024-08-22 13:22 ` |FAILURE| " dpdklab
2024-08-22 13:24 ` |SUCCESS| " dpdklab
2024-08-22 13:25 ` dpdklab
2024-08-22 13:46 ` dpdklab
2024-08-22 13:56 ` |WARNING| " dpdklab
2024-08-22 13:57 ` |PENDING| " dpdklab
2024-08-22 14:34 ` |SUCCESS| " dpdklab
2024-08-22 14:36 ` dpdklab
2024-08-22 15:10 ` dpdklab
2024-08-22 15:37 ` dpdklab
2024-08-22 16:08 ` dpdklab
2024-08-22 18:33 ` dpdklab
2024-08-22 18:42 ` dpdklab
2024-08-22 18:42 ` dpdklab
2024-09-21  4:08 ` dpdklab
2024-09-21  4:20 ` dpdklab
2024-09-21  4:43 ` dpdklab
2024-09-21  5:05 ` 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=66c72842.170a0220.1a80c4.4af7SMTPIN_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).