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| pw130155-130156 [PATCH] [v2,2/2] test/crypto: add security
Date: Sat, 12 Aug 2023 00:00:31 -0700 (PDT)	[thread overview]
Message-ID: <64d72e0f.9f0a0220.720d7.0a68SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: David Coyle <david.coyle@intel.com>
Date: Friday, August 11 2023 10:24:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130155-130156 --> testing pass

Test environment and result as below:

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


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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-12  7:00 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12  7:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-13 21:47 dpdklab
2023-08-13 21:46 dpdklab
2023-08-13 21:39 dpdklab
2023-08-13 21:36 dpdklab
2023-08-13 21:36 dpdklab
2023-08-13 21:35 dpdklab
2023-08-13 21:34 dpdklab
2023-08-13 21:33 dpdklab
2023-08-13 21:31 dpdklab
2023-08-13 21:30 dpdklab
2023-08-13 21:29 dpdklab
2023-08-13 19:56 dpdklab
2023-08-13 19:00 dpdklab
2023-08-12  6:37 dpdklab
2023-08-12  6:27 dpdklab
2023-08-12  6:10 dpdklab
2023-08-12  6:05 dpdklab
2023-08-12  6:00 dpdklab
2023-08-12  1:26 dpdklab
2023-08-12  0:05 dpdklab
2023-08-12  0:04 dpdklab
2023-08-12  0:02 dpdklab
2023-08-12  0:01 dpdklab
2023-08-11 23:57 dpdklab
2023-08-11 22:35 dpdklab
2023-08-11 22:35 dpdklab
2023-08-11 22:34 dpdklab
2023-08-11 15:07 dpdklab
2023-08-11 15:05 dpdklab
2023-08-11 15:04 dpdklab
2023-08-11 15:02 dpdklab
2023-08-11 15:01 dpdklab
2023-08-11 14:58 dpdklab
2023-08-11 14:58 dpdklab
2023-08-11 14:56 dpdklab
2023-08-11 14:50 dpdklab
2023-08-11 14:33 dpdklab
2023-08-11 14:27 dpdklab
2023-08-11 14:26 dpdklab
2023-08-11 14:23 dpdklab
2023-08-11 14:21 dpdklab
2023-08-11 14:11 dpdklab
2023-08-11 14:06 dpdklab
2023-08-11 14:01 dpdklab
2023-08-11 13:38 dpdklab
2023-08-11 13:37 dpdklab
2023-08-11 13:11 dpdklab
2023-08-11 13:09 dpdklab
2023-08-11 13:09 dpdklab
2023-08-11 13:09 dpdklab
2023-08-11 13:09 dpdklab
2023-08-11 13:09 dpdklab
2023-08-11 13:09 dpdklab
2023-08-11 13:07 dpdklab
2023-08-11 13:07 dpdklab
2023-08-11 13:07 dpdklab
2023-08-11 13:06 dpdklab
2023-08-11 13:06 dpdklab
2023-08-11 13:06 dpdklab
2023-08-11 13:06 dpdklab
2023-08-11 13:06 dpdklab
2023-08-11 13:06 dpdklab
2023-08-11 13:06 dpdklab
2023-08-11 13:05 dpdklab
2023-08-11 13:05 dpdklab
2023-08-11 13:05 dpdklab
2023-08-11 13:05 dpdklab
2023-08-11 13:05 dpdklab
2023-08-11 13:04 dpdklab
2023-08-11 13:04 dpdklab
2023-08-11 13:03 dpdklab
2023-08-11 13:03 dpdklab
2023-08-11 13:03 dpdklab
2023-08-11 12:59 dpdklab
2023-08-11 12:58 dpdklab
2023-08-11 12:47 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=64d72e0f.9f0a0220.720d7.0a68SMTPIN_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).