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| pw128374-128384 [PATCH] [v3,13/13] test/security: remove n
Date: Thu, 08 Jun 2023 21:08:21 -0700 (PDT)	[thread overview]
Message-ID: <6482a5b5.050a0220.f1eb.3e2fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Thursday, June 08 2023 06:54:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:55ead98d1de1b02fa563e822a67c7adc0361ddfb

128374-128384 --> 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/26584/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-09  4:08 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  4:08 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-16 21:22 dpdklab
2023-06-16 21:21 dpdklab
2023-06-16 21:08 dpdklab
2023-06-16 21:06 dpdklab
2023-06-16 21:05 dpdklab
2023-06-16 21:05 dpdklab
2023-06-16 21:02 dpdklab
2023-06-16 21:01 dpdklab
2023-06-16 21:00 dpdklab
2023-06-16 20:57 dpdklab
2023-06-10  1:48 dpdklab
2023-06-09 13:46 dpdklab
2023-06-09 13:44 dpdklab
2023-06-09 13:40 dpdklab
2023-06-09  6:39 dpdklab
2023-06-09  6:38 dpdklab
2023-06-09  6:21 dpdklab
2023-06-09  6:17 dpdklab
2023-06-09  6:00 dpdklab
2023-06-09  4:08 dpdklab
2023-06-09  2:40 dpdklab
2023-06-09  0:42 dpdklab
2023-06-08 22:39 dpdklab
2023-06-08 22:39 dpdklab
2023-06-08 22:36 dpdklab
2023-06-08 22:36 dpdklab
2023-06-08 22:35 dpdklab
2023-06-08 22:35 dpdklab
2023-06-08 22:35 dpdklab
2023-06-08 22:35 dpdklab
2023-06-08 22:35 dpdklab
2023-06-08 22:35 dpdklab
2023-06-08 21:53 dpdklab
2023-06-08 21:40 dpdklab
2023-06-08 21:31 dpdklab
2023-06-08 21:25 dpdklab
2023-06-08 19:58 dpdklab
2023-06-08 19:58 dpdklab
2023-06-08 19:55 dpdklab
2023-06-08 19:52 dpdklab
2023-06-08 19:52 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=6482a5b5.050a0220.f1eb.3e2fSMTPIN_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).