automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125072-125073 [PATCH] [v3, 2/2] crypto/qat: add cipher-crc offload support
Date: Tue, 14 Mar 2023 08:57:32 +0000 (UTC)	[thread overview]
Message-ID: <20230314085732.785306011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125073

_Testing PASS_

Submitter: Kevin O'Sullivan <kevin.osullivan@intel.com>
Date: Monday, March 13 2023 14:26:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:baf13c3135d0c5998fff7edc23fb89412dc89246

125072-125073 --> testing pass

Test environment and result as below:

+--------------+----------------------+
| Environment  | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS                 |
+--------------+----------------------+


Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-14  8:57 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  8:57 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-15  8:39 dpdklab
2023-03-15  6:02 dpdklab
2023-03-14 11:24 dpdklab
2023-03-14 11:23 dpdklab
2023-03-14 10:39 dpdklab
2023-03-14 10:37 dpdklab
2023-03-14 10:35 dpdklab
2023-03-14 10:32 dpdklab
2023-03-14 10:29 dpdklab
2023-03-14 10:28 dpdklab
2023-03-14 10:22 dpdklab
2023-03-14 10:21 dpdklab
2023-03-14 10:19 dpdklab
2023-03-14 10:17 dpdklab
2023-03-14 10:01 dpdklab
2023-03-14  8:57 dpdklab
2023-03-14  8:52 dpdklab
2023-03-14  8:33 dpdklab
2023-03-14  8:22 dpdklab
2023-03-14  8:20 dpdklab
2023-03-14  8:18 dpdklab
2023-03-14  8:16 dpdklab
2023-03-14  8:15 dpdklab
2023-03-14  8:13 dpdklab
2023-03-14  7:56 dpdklab
2023-03-14  7:55 dpdklab
2023-03-14  7:46 dpdklab
2023-03-13 22:59 dpdklab
2023-03-13 20:21 dpdklab
2023-03-13 20:05 dpdklab
2023-03-13 19:18 dpdklab
2023-03-13 19:02 dpdklab
2023-03-13 19:02 dpdklab
2023-03-13 18:56 dpdklab
2023-03-13 18:51 dpdklab
2023-03-13 18:44 dpdklab
2023-03-13 18:41 dpdklab
2023-03-13 18:39 dpdklab
2023-03-13 18:36 dpdklab
2023-03-13 18:34 dpdklab
2023-03-13 18:22 dpdklab
2023-03-13 18:22 dpdklab
2023-03-13 18:22 dpdklab
2023-03-13 18:19 dpdklab
2023-03-13 18:12 dpdklab
2023-03-13 18:10 dpdklab
2023-03-13 18:01 dpdklab
2023-03-13 17:55 dpdklab
2023-03-13 17:54 dpdklab
2023-03-13 17:51 dpdklab
2023-03-13 17:45 dpdklab
2023-03-13 17:43 dpdklab
2023-03-13 17:42 dpdklab
2023-03-13 17:40 dpdklab
2023-03-13 17:38 dpdklab
2023-03-13 17:37 dpdklab
2023-03-13 17:36 dpdklab
2023-03-13 17:30 dpdklab
     [not found] <20230313142603.234169-3-kevin.osullivan@intel.com>
2023-03-13 14:17 ` |SUCCESS| pw125072-125073 [PATCH v3 " qemudev
2023-03-13 14:21 ` qemudev

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=20230314085732.785306011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).