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| pw139223-139225 [PATCH] [3/3] test/crypto: add QP depth us
Date: Thu, 11 Apr 2024 02:56:38 -0700 (PDT)	[thread overview]
Message-ID: <6617b3d6.d40a0220.ed83f.5c34SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240411082232.3495883-4-gakhil@marvell.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139225

_Testing PASS_

Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Thursday, April 11 2024 08:22:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139223-139225 --> testing pass

Test environment and result as below:

+--------------------------+----------------+
|       Environment        | dpdk_unit_test |
+==========================+================+
| Debian 11 (Buster) (ARM) | PASS           |
+--------------------------+----------------+
| Fedora 38 (ARM)          | PASS           |
+--------------------------+----------------+
| CentOS Stream 9 (ARM)    | PASS           |
+--------------------------+----------------+


Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-11  9:56 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240411082232.3495883-4-gakhil@marvell.com>
2024-04-11  7:59 ` |SUCCESS| pw139223-139225 [PATCH 3/3] test/crypto: add QP depth used count case qemudev
2024-04-11  8:04 ` qemudev
2024-04-11  8:23 ` |SUCCESS| pw139225 " checkpatch
2024-04-11  9:23 ` |FAILURE| " 0-day Robot
2024-04-11  9:52 ` |SUCCESS| pw139223-139225 [PATCH] [3/3] test/crypto: add QP depth us dpdklab
2024-04-11  9:53 ` dpdklab
2024-04-11  9:54 ` dpdklab
2024-04-11  9:54 ` dpdklab
2024-04-11  9:54 ` dpdklab
2024-04-11  9:54 ` dpdklab
2024-04-11  9:55 ` dpdklab
2024-04-11  9:55 ` dpdklab
2024-04-11  9:55 ` dpdklab
2024-04-11  9:56 ` dpdklab
2024-04-11  9:56 ` dpdklab
2024-04-11  9:56 ` dpdklab [this message]
2024-04-11  9:57 ` dpdklab
2024-04-11  9:57 ` dpdklab
2024-04-11  9:58 ` dpdklab
2024-04-11  9:58 ` dpdklab
2024-04-11  9:59 ` dpdklab
2024-04-11  9:59 ` dpdklab
2024-04-11  9:59 ` dpdklab
2024-04-11  9:59 ` dpdklab
2024-04-11  9:59 ` dpdklab
2024-04-11  9:59 ` dpdklab
2024-04-11 10:00 ` dpdklab
2024-04-11 10:01 ` dpdklab
2024-04-11 10:01 ` dpdklab
2024-04-11 10:01 ` dpdklab
2024-04-11 10:02 ` dpdklab
2024-04-11 10:02 ` dpdklab
2024-04-11 10:02 ` dpdklab
2024-04-11 10:02 ` dpdklab
2024-04-11 10:02 ` dpdklab
2024-04-11 10:03 ` dpdklab
2024-04-11 10:03 ` dpdklab
2024-04-11 10:04 ` dpdklab
2024-04-11 10:05 ` dpdklab
2024-04-11 10:05 ` dpdklab
2024-04-11 10:06 ` dpdklab
2024-04-11 10:06 ` dpdklab
2024-04-11 10:07 ` dpdklab
2024-04-11 10:08 ` dpdklab
2024-04-11 10:09 ` dpdklab
2024-04-11 10:10 ` dpdklab
2024-04-11 10:11 ` dpdklab
2024-04-11 10:11 ` dpdklab
2024-04-11 10:11 ` dpdklab
2024-04-11 10:12 ` dpdklab
2024-04-11 10:13 ` dpdklab
2024-04-11 10:13 ` dpdklab
2024-04-11 10:13 ` dpdklab
2024-04-11 10:14 ` dpdklab
2024-04-11 10:15 ` dpdklab
2024-04-11 10:16 ` dpdklab
2024-04-11 10:17 ` dpdklab
2024-04-11 10:18 ` dpdklab
2024-04-11 10:19 ` dpdklab
2024-04-11 10:19 ` dpdklab
2024-04-11 10:20 ` dpdklab
2024-04-11 10:22 ` dpdklab
2024-04-11 10:22 ` dpdklab
2024-04-11 10:23 ` dpdklab
2024-04-11 10:24 ` dpdklab
2024-04-11 10:24 ` dpdklab
2024-04-11 10:25 ` dpdklab
2024-04-11 10:25 ` dpdklab
2024-04-11 10:25 ` dpdklab
2024-04-11 10:25 ` dpdklab
2024-04-11 10:27 ` dpdklab
2024-04-11 10:27 ` dpdklab
2024-04-11 10:28 ` dpdklab
2024-04-11 10:29 ` dpdklab
2024-04-11 10:29 ` dpdklab
2024-04-11 10:31 ` dpdklab
2024-04-11 10:32 ` dpdklab
2024-04-11 10:33 ` dpdklab
2024-04-11 10:37 ` dpdklab
2024-04-11 10:39 ` dpdklab
2024-04-11 10:41 ` dpdklab
2024-04-11 10:45 ` dpdklab
2024-04-11 10:49 ` dpdklab
2024-04-11 11:04 ` dpdklab
2024-04-11 11:08 ` dpdklab
2024-04-11 11:12 ` dpdklab
2024-04-11 11:16 ` dpdklab
2024-04-11 11:16 ` dpdklab
2024-04-11 11:35 ` dpdklab
2024-04-11 12:58 ` dpdklab
2024-04-11 13:44 ` dpdklab
2024-04-11 14:22 ` 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=6617b3d6.d40a0220.ed83f.5c34SMTPIN_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).