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| pw141948-141949 [PATCH] [v3,2/2] cryptodev: validate crypt
Date: Thu, 27 Jun 2024 08:29:00 -0700 (PDT)	[thread overview]
Message-ID: <667d853c.050a0220.8ccc5.2da3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240627100626.2430162-2-ganapati.kundapura@intel.com>

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

_Functional Testing PASS_

Submitter: Kundapura, Ganapati <ganapati.kundapura@intel.com>
Date: Thursday, June 27 2024 10:06:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b80379078a1f7c09b8d0ece24442c8ff2e2c67c

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


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

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-27 15:29 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240627100626.2430162-2-ganapati.kundapura@intel.com>
2024-06-27  9:42 ` |SUCCESS| pw141948-141949 [PATCH v3 2/2] cryptodev: validate crypto callbacks from next node qemudev
2024-06-27  9:46 ` qemudev
2024-06-27 10:09 ` |SUCCESS| pw141949 " checkpatch
2024-06-27 11:06 ` 0-day Robot
2024-06-27 13:35 ` |SUCCESS| pw141948-141949 [PATCH] [v3,2/2] cryptodev: validate crypt dpdklab
2024-06-27 13:49 ` dpdklab
2024-06-27 14:02 ` dpdklab
2024-06-27 14:04 ` dpdklab
2024-06-27 14:17 ` dpdklab
2024-06-27 14:27 ` dpdklab
2024-06-27 14:34 ` dpdklab
2024-06-27 14:35 ` dpdklab
2024-06-27 14:36 ` |PENDING| " dpdklab
2024-06-27 14:37 ` dpdklab
2024-06-27 14:37 ` dpdklab
2024-06-27 14:38 ` dpdklab
2024-06-27 14:39 ` dpdklab
2024-06-27 14:41 ` dpdklab
2024-06-27 14:42 ` dpdklab
2024-06-27 14:43 ` dpdklab
2024-06-27 14:44 ` dpdklab
2024-06-27 14:46 ` dpdklab
2024-06-27 14:47 ` dpdklab
2024-06-27 14:50 ` dpdklab
2024-06-27 14:53 ` dpdklab
2024-06-27 14:56 ` |SUCCESS| " dpdklab
2024-06-27 14:58 ` |PENDING| " dpdklab
2024-06-27 15:00 ` |SUCCESS| " dpdklab
2024-06-27 15:01 ` dpdklab
2024-06-27 15:05 ` dpdklab
2024-06-27 15:22 ` dpdklab
2024-06-27 15:29 ` dpdklab [this message]
2024-06-27 15:29 ` dpdklab
2024-06-27 15:33 ` dpdklab
2024-06-27 15:43 ` dpdklab
2024-06-27 15:53 ` dpdklab
2024-06-27 17:30 ` dpdklab
2024-06-27 17:30 ` dpdklab
2024-06-27 17:31 ` dpdklab
2024-06-27 17:32 ` dpdklab
2024-06-27 17:34 ` dpdklab
2024-06-27 17:51 ` dpdklab
2024-06-27 18:34 ` dpdklab
2024-06-27 19:07 ` dpdklab
2024-06-27 19:12 ` dpdklab
2024-06-27 19:12 ` dpdklab
2024-06-27 19:21 ` dpdklab
2024-06-27 19:23 ` dpdklab
2024-06-27 19:24 ` dpdklab
2024-06-27 19:33 ` dpdklab
2024-06-27 19:33 ` dpdklab
2024-06-27 19:51 ` dpdklab
2024-06-27 19:56 ` dpdklab
2024-06-27 19:57 ` dpdklab
2024-06-27 19:59 ` dpdklab
2024-06-27 20:01 ` dpdklab
2024-06-27 20:04 ` dpdklab
2024-06-27 20:10 ` dpdklab
2024-06-27 20:15 ` dpdklab
2024-06-27 20:20 ` dpdklab
2024-06-27 20:27 ` dpdklab
2024-06-27 20:28 ` dpdklab
2024-06-27 20:38 ` dpdklab
2024-06-27 20:41 ` dpdklab
2024-06-27 20:47 ` dpdklab
2024-06-27 20:53 ` dpdklab
2024-06-27 20:57 ` dpdklab
2024-06-27 21:02 ` dpdklab
2024-06-27 21:02 ` dpdklab
2024-06-27 21:05 ` dpdklab
2024-06-27 21:05 ` dpdklab
2024-06-27 21:05 ` dpdklab
2024-06-27 21:08 ` dpdklab
2024-06-27 21:23 ` dpdklab
2024-06-27 21:33 ` dpdklab
2024-06-27 21:44 ` dpdklab
2024-06-27 21:46 ` dpdklab
2024-06-27 21:47 ` dpdklab
2024-06-27 21:50 ` dpdklab
2024-06-27 21:52 ` dpdklab
2024-06-27 21:56 ` dpdklab
2024-06-27 21:58 ` dpdklab
2024-06-27 22:03 ` dpdklab
2024-06-27 22:11 ` dpdklab
2024-06-27 22:14 ` dpdklab
2024-06-27 22:14 ` dpdklab
2024-06-27 22:15 ` dpdklab
2024-06-27 22:16 ` dpdklab
2024-06-27 22:17 ` dpdklab
2024-06-27 22:20 ` dpdklab
2024-06-27 22:21 ` dpdklab
2024-06-27 22:22 ` dpdklab
2024-06-27 22:22 ` dpdklab
2024-06-27 22:23 ` dpdklab
2024-06-27 22:24 ` dpdklab
2024-06-27 22:29 ` dpdklab
2024-06-27 22:34 ` dpdklab
2024-06-27 22:34 ` dpdklab
2024-06-27 22:34 ` dpdklab
2024-06-27 22:35 ` dpdklab
2024-06-27 22:37 ` dpdklab
2024-06-27 22:39 ` dpdklab
2024-06-27 22:39 ` dpdklab
2024-06-27 22:40 ` dpdklab
2024-06-27 22:43 ` dpdklab
2024-06-27 22:44 ` dpdklab
2024-06-27 22:48 ` dpdklab
2024-06-27 23:03 ` dpdklab
2024-06-27 23:03 ` dpdklab
2024-06-27 23:05 ` dpdklab
2024-06-27 23:05 ` dpdklab
2024-06-28  9:07 ` dpdklab
2024-06-28  9:25 ` dpdklab
2024-06-29  1:01 ` 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=667d853c.050a0220.8ccc5.2da3SMTPIN_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).