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] 1025bd1c24b1be70e028c7ba0595782bce75fcc6
Date: Thu, 02 Nov 2023 06:22:48 -0700 (PDT)	[thread overview]
Message-ID: <6543a2a8.170a0220.e076b.a085SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

1025bd1c24b1be70e028c7ba0595782bce75fcc6 --> 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/tarballs/26775/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-02 13:22 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 13:22 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-02  9:23 dpdklab
2023-11-02  3:59 dpdklab
2023-11-02  3:58 dpdklab
2023-11-02  3:23 dpdklab
2023-11-02  3:21 dpdklab
2023-11-02  3:06 dpdklab
2023-11-02  3:06 dpdklab
2023-11-02  3:04 dpdklab
2023-11-02  3:03 dpdklab
2023-11-02  3:03 dpdklab
2023-11-02  3:03 dpdklab
2023-11-02  3:03 dpdklab
2023-11-02  3:01 dpdklab
2023-11-02  2:59 dpdklab
2023-11-02  2:52 dpdklab
2023-11-02  2:26 dpdklab
2023-11-02  2:22 dpdklab
2023-11-02  2:22 dpdklab
2023-11-02  2:22 dpdklab
2023-11-02  2:22 dpdklab
2023-11-02  2:22 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:21 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:16 dpdklab
2023-11-02  2:15 dpdklab
2023-11-02  2:15 dpdklab
2023-11-02  2:15 dpdklab
2023-11-02  2:08 dpdklab
2023-11-02  2:07 dpdklab
2023-11-02  2:05 dpdklab
2023-11-02  2:04 dpdklab
2023-11-02  1:51 dpdklab
2023-11-02  1:47 dpdklab
2023-11-02  1:37 dpdklab
2023-11-02  1:35 dpdklab
2023-11-02  1:34 dpdklab
2023-11-02  1:28 dpdklab
2023-11-01  3:58 dpdklab
2023-11-01  3:05 dpdklab
2023-11-01  1:59 dpdklab
2023-11-01  1:56 dpdklab
2023-11-01  1:53 dpdklab
2023-11-01  1:53 dpdklab
2023-11-01  1:52 dpdklab
2023-11-01  1:52 dpdklab
2023-11-01  1:51 dpdklab
2023-11-01  1:44 dpdklab
2023-11-01  1:29 dpdklab
2023-11-01  1:23 dpdklab
2023-11-01  1:22 dpdklab
2023-11-01  1:21 dpdklab
2023-11-01  1:20 dpdklab
2023-11-01  1:20 dpdklab
2023-11-01  1:20 dpdklab
2023-11-01  1:19 dpdklab
2023-11-01  1:17 dpdklab
2023-11-01  1:16 dpdklab
2023-11-01  1:15 dpdklab
2023-11-01  1:14 dpdklab
2023-11-01  1:14 dpdklab
2023-11-01  1:14 dpdklab
2023-11-01  1:14 dpdklab
2023-11-01  1:13 dpdklab
2023-11-01  1:12 dpdklab
2023-11-01  1:12 dpdklab
2023-11-01  1:12 dpdklab
2023-11-01  1:11 dpdklab
2023-11-01  1:11 dpdklab
2023-11-01  1:11 dpdklab
2023-11-01  1:11 dpdklab
2023-11-01  1:11 dpdklab
2023-11-01  1:11 dpdklab
2023-11-01  1:10 dpdklab
2023-11-01  1:10 dpdklab
2023-11-01  1:10 dpdklab
2023-11-01  1:10 dpdklab
2023-11-01  1:09 dpdklab
2023-11-01  1:09 dpdklab
2023-11-01  1:09 dpdklab
2023-11-01  1:09 dpdklab
2023-11-01  1:09 dpdklab
2023-11-01  1:09 dpdklab
2023-11-01  1:08 dpdklab
2023-11-01  1:08 dpdklab
2023-11-01  1:07 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=6543a2a8.170a0220.e076b.a085SMTPIN_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).