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| pw142324 [PATCH] [v1] crypto/aesni_mb: fix typo in error m
Date: Thu, 11 Jul 2024 14:03:10 -0700 (PDT)	[thread overview]
Message-ID: <6690488e.170a0220.dff87.029eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240711131457.959498-1-joel.kavanagh@intel.com>

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142324

_Testing PASS_

Submitter: Joel Kavanagh <joel.kavanagh@intel.com>
Date: Thursday, July 11 2024 13:14:57 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ba268b0bb43b56174e3d9345a27e6b1675a5a991

142324 --> testing pass

Test environment and result as below:

+--------------------+----------------------+----------------------+
|    Environment     | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04       | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04       | SKIPPED              | PASS                 |
+--------------------+----------------------+----------------------+


Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04
	Kernel: 5.15.0-100-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

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-11 21:03 UTC|newest]

Thread overview: 119+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240711131457.959498-1-joel.kavanagh@intel.com>
2024-07-11 14:16 ` |SUCCESS| pw142324 [PATCH v1] crypto/aesni_mb: fix typo in error message qemudev
2024-07-11 14:20 ` qemudev
2024-07-11 14:44 ` |WARNING| " checkpatch
2024-07-11 15:20 ` |PENDING| pw142324 [PATCH] [v1] crypto/aesni_mb: fix typo in error m dpdklab
2024-07-11 15:23 ` dpdklab
2024-07-11 15:27 ` |SUCCESS| " dpdklab
2024-07-11 15:27 ` |PENDING| " dpdklab
2024-07-11 15:27 ` |SUCCESS| " dpdklab
2024-07-11 15:30 ` dpdklab
2024-07-11 15:31 ` dpdklab
2024-07-11 15:39 ` dpdklab
2024-07-11 15:40 ` dpdklab
2024-07-11 15:41 ` dpdklab
2024-07-11 15:43 ` |SUCCESS| pw142324 [PATCH v1] crypto/aesni_mb: fix typo in error message 0-day Robot
2024-07-11 15:43 ` |PENDING| pw142324 [PATCH] [v1] crypto/aesni_mb: fix typo in error m dpdklab
2024-07-11 15:43 ` |SUCCESS| " dpdklab
2024-07-11 15:44 ` |PENDING| " dpdklab
2024-07-11 15:47 ` |SUCCESS| " dpdklab
2024-07-11 15:49 ` |PENDING| " dpdklab
2024-07-11 15:50 ` dpdklab
2024-07-11 15:50 ` dpdklab
2024-07-11 15:51 ` dpdklab
2024-07-11 15:51 ` dpdklab
2024-07-11 15:52 ` dpdklab
2024-07-11 15:54 ` dpdklab
2024-07-11 15:54 ` dpdklab
2024-07-11 15:57 ` dpdklab
2024-07-11 15:59 ` dpdklab
2024-07-11 16:00 ` dpdklab
2024-07-11 16:01 ` dpdklab
2024-07-11 16:02 ` dpdklab
2024-07-11 16:03 ` dpdklab
2024-07-11 16:04 ` dpdklab
2024-07-11 16:04 ` dpdklab
2024-07-11 16:05 ` |SUCCESS| " dpdklab
2024-07-11 16:05 ` |PENDING| " dpdklab
2024-07-11 16:10 ` dpdklab
2024-07-11 16:12 ` dpdklab
2024-07-11 16:16 ` dpdklab
2024-07-11 16:19 ` dpdklab
2024-07-11 16:19 ` dpdklab
2024-07-11 16:22 ` dpdklab
2024-07-11 16:23 ` dpdklab
2024-07-11 16:23 ` dpdklab
2024-07-11 16:23 ` dpdklab
2024-07-11 16:24 ` dpdklab
2024-07-11 16:25 ` dpdklab
2024-07-11 16:25 ` dpdklab
2024-07-11 16:26 ` dpdklab
2024-07-11 16:30 ` dpdklab
2024-07-11 16:31 ` |SUCCESS| " dpdklab
2024-07-11 16:33 ` |PENDING| " dpdklab
2024-07-11 16:36 ` dpdklab
2024-07-11 16:37 ` dpdklab
2024-07-11 16:37 ` dpdklab
2024-07-11 16:37 ` dpdklab
2024-07-11 16:39 ` dpdklab
2024-07-11 16:40 ` dpdklab
2024-07-11 16:40 ` dpdklab
2024-07-11 16:43 ` dpdklab
2024-07-11 16:45 ` dpdklab
2024-07-11 16:46 ` dpdklab
2024-07-11 16:47 ` dpdklab
2024-07-11 16:48 ` dpdklab
2024-07-11 16:48 ` dpdklab
2024-07-11 16:52 ` dpdklab
2024-07-11 16:52 ` dpdklab
2024-07-11 16:52 ` dpdklab
2024-07-11 16:53 ` dpdklab
2024-07-11 16:54 ` dpdklab
2024-07-11 16:55 ` dpdklab
2024-07-11 16:56 ` dpdklab
2024-07-11 16:56 ` dpdklab
2024-07-11 16:57 ` dpdklab
2024-07-11 16:57 ` dpdklab
2024-07-11 17:02 ` dpdklab
2024-07-11 17:05 ` dpdklab
2024-07-11 17:05 ` dpdklab
2024-07-11 17:06 ` dpdklab
2024-07-11 17:06 ` dpdklab
2024-07-11 17:07 ` dpdklab
2024-07-11 17:09 ` dpdklab
2024-07-11 17:14 ` dpdklab
2024-07-11 17:15 ` dpdklab
2024-07-11 17:19 ` dpdklab
2024-07-11 17:20 ` dpdklab
2024-07-11 17:20 ` dpdklab
2024-07-11 17:20 ` |SUCCESS| " dpdklab
2024-07-11 17:21 ` dpdklab
2024-07-11 17:21 ` |PENDING| " dpdklab
2024-07-11 17:24 ` dpdklab
2024-07-11 17:26 ` dpdklab
2024-07-11 17:27 ` dpdklab
2024-07-11 17:30 ` dpdklab
2024-07-11 17:32 ` dpdklab
2024-07-11 17:36 ` dpdklab
2024-07-11 17:37 ` dpdklab
2024-07-11 17:38 ` dpdklab
2024-07-11 17:38 ` dpdklab
2024-07-11 17:39 ` dpdklab
2024-07-11 17:39 ` dpdklab
2024-07-11 17:39 ` dpdklab
2024-07-11 17:39 ` dpdklab
2024-07-11 17:39 ` dpdklab
2024-07-11 17:39 ` dpdklab
2024-07-11 17:41 ` dpdklab
2024-07-11 17:42 ` dpdklab
2024-07-11 17:47 ` dpdklab
2024-07-11 17:48 ` dpdklab
2024-07-11 17:48 ` |SUCCESS| " dpdklab
2024-07-11 17:48 ` |PENDING| " dpdklab
2024-07-11 17:55 ` |SUCCESS| " dpdklab
2024-07-11 18:10 ` dpdklab
2024-07-11 21:03 ` dpdklab [this message]
2024-07-13  2:08 ` dpdklab
2024-07-14  6:56 ` dpdklab
2024-07-14 13:19 ` dpdklab
2024-07-14 21:57 ` dpdklab
2024-07-14 22: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=6690488e.170a0220.dff87.029eSMTPIN_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).