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| [GIT MASTER] dbff181d62c997f128b75db2bbac9f42e8dd0f8f
Date: Sun, 14 May 2023 19:35:19 -0700 (PDT)	[thread overview]
Message-ID: <64619a67.050a0220.d753e.806eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

dbff181d62c997f128b75db2bbac9f42e8dd0f8f --> 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/tarballs/24552/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-15  2:35 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15  2:35 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-15  2:43 dpdklab
2023-05-15  2:42 dpdklab
2023-05-15  2:38 dpdklab
2023-05-15  2:36 dpdklab
2023-05-15  2:35 dpdklab
2023-05-15  2:16 dpdklab
2023-05-15  2:10 dpdklab
2023-05-15  1:49 dpdklab
2023-05-15  1:45 dpdklab
2023-05-15  1:37 dpdklab
2023-05-15  1:35 dpdklab
2023-05-15  1:32 dpdklab
2023-05-15  1:31 dpdklab
2023-05-15  1:28 dpdklab
2023-05-15  1:27 dpdklab
2023-05-15  1:24 dpdklab
2023-05-15  1:23 dpdklab
2023-05-15  1:22 dpdklab
2023-05-15  1:18 dpdklab
2023-05-15  1:10 dpdklab
2023-05-15  1:10 dpdklab
2023-05-15  1:03 dpdklab
2023-05-15  1:03 dpdklab
2023-05-15  1:03 dpdklab
2023-05-15  1:02 dpdklab
2023-05-15  1:02 dpdklab
2023-05-15  0:59 dpdklab
2023-05-15  0:57 dpdklab
2023-05-14  2:28 dpdklab
2023-05-14  2:21 dpdklab
2023-05-14  2:21 dpdklab
2023-05-14  2:20 dpdklab
2023-05-14  2:19 dpdklab
2023-05-14  2:13 dpdklab
2023-05-14  2:05 dpdklab
2023-05-14  1:53 dpdklab
2023-05-14  1:51 dpdklab
2023-05-14  1:44 dpdklab
2023-05-14  1:40 dpdklab
2023-05-14  1:37 dpdklab
2023-05-14  1:34 dpdklab
2023-05-14  1:31 dpdklab
2023-05-14  1:27 dpdklab
2023-05-14  1:23 dpdklab
2023-05-14  1:23 dpdklab
2023-05-14  1:18 dpdklab
2023-05-14  1:18 dpdklab
2023-05-14  1:10 dpdklab
2023-05-14  1:09 dpdklab
2023-05-14  1:07 dpdklab
2023-05-14  1:04 dpdklab
2023-05-14  1:03 dpdklab
2023-05-14  1:03 dpdklab
2023-05-14  1:03 dpdklab
2023-05-14  1:02 dpdklab
2023-05-14  0:58 dpdklab
2023-05-14  0:56 dpdklab
2023-05-13  4:44 dpdklab
2023-05-13  4:39 dpdklab
2023-05-13  4:30 dpdklab
2023-05-13  4:25 dpdklab
2023-05-13  4:21 dpdklab
2023-05-13  2:30 dpdklab
2023-05-13  2:15 dpdklab
2023-05-13  2:12 dpdklab
2023-05-13  2:10 dpdklab
2023-05-13  2:02 dpdklab
2023-05-13  1:57 dpdklab
2023-05-13  1:35 dpdklab
2023-05-13  1:34 dpdklab
2023-05-13  1:34 dpdklab
2023-05-13  1:30 dpdklab
2023-05-13  1:29 dpdklab
2023-05-13  1:25 dpdklab
2023-05-13  1:24 dpdklab
2023-05-13  1:15 dpdklab
2023-05-13  1:12 dpdklab
2023-05-13  1:09 dpdklab
2023-05-13  1:05 dpdklab
2023-05-13  1:04 dpdklab
2023-05-13  1:03 dpdklab
2023-05-13  1:00 dpdklab
2023-05-13  0:57 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=64619a67.050a0220.d753e.806eSMTPIN_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).