From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 2ecc673e5e9a19850ba76d6a976596890f2dade1
Date: Sat, 27 Jan 2024 18:25:43 -0800 (PST) [thread overview]
Message-ID: <65b5bb27.810a0220.2bfce.58efSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
2ecc673e5e9a19850ba76d6a976596890f2dade1 --> 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/27815/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-28 2:25 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 2:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-28 4:41 dpdklab
2024-01-28 2:50 dpdklab
2024-01-28 2:46 dpdklab
2024-01-28 2:26 dpdklab
2024-01-28 2:23 dpdklab
2024-01-28 2:21 dpdklab
2024-01-28 2:21 dpdklab
2024-01-28 2:20 dpdklab
2024-01-28 2:20 dpdklab
2024-01-28 2:19 dpdklab
2024-01-28 2:16 dpdklab
2024-01-28 2:16 dpdklab
2024-01-28 2:16 dpdklab
2024-01-28 2:14 dpdklab
2024-01-28 2:13 dpdklab
2024-01-28 2:12 dpdklab
2024-01-28 2:12 dpdklab
2024-01-28 2:10 dpdklab
2024-01-28 2:07 dpdklab
2024-01-28 2:07 dpdklab
2024-01-28 2:05 dpdklab
2024-01-28 2:05 dpdklab
2024-01-28 2:05 dpdklab
2024-01-28 2:05 dpdklab
2024-01-28 2:05 dpdklab
2024-01-28 2:05 dpdklab
2024-01-28 2:04 dpdklab
2024-01-28 2:04 dpdklab
2024-01-28 2:03 dpdklab
2024-01-28 2:03 dpdklab
2024-01-28 2:00 dpdklab
2024-01-28 2:00 dpdklab
2024-01-28 2:00 dpdklab
2024-01-28 2:00 dpdklab
2024-01-28 2:00 dpdklab
2024-01-28 1:59 dpdklab
2024-01-28 1:59 dpdklab
2024-01-28 1:58 dpdklab
2024-01-28 1:57 dpdklab
2024-01-28 1:56 dpdklab
2024-01-28 1:56 dpdklab
2024-01-28 1:56 dpdklab
2024-01-28 1:55 dpdklab
2024-01-28 1:55 dpdklab
2024-01-28 1:55 dpdklab
2024-01-28 1:54 dpdklab
2024-01-28 1:54 dpdklab
2024-01-28 1:53 dpdklab
2024-01-28 1:53 dpdklab
2024-01-28 1:53 dpdklab
2024-01-28 1:52 dpdklab
2024-01-28 1:52 dpdklab
2024-01-28 1:52 dpdklab
2024-01-28 1:51 dpdklab
2024-01-26 4:46 dpdklab
2024-01-26 2:52 dpdklab
2024-01-26 2:32 dpdklab
2024-01-26 2:28 dpdklab
2024-01-26 2:25 dpdklab
2024-01-26 2:23 dpdklab
2024-01-26 2:22 dpdklab
2024-01-26 2:21 dpdklab
2024-01-26 2:19 dpdklab
2024-01-26 2:18 dpdklab
2024-01-26 2:17 dpdklab
2024-01-26 2:16 dpdklab
2024-01-26 2:16 dpdklab
2024-01-26 2:14 dpdklab
2024-01-26 2:14 dpdklab
2024-01-26 2:12 dpdklab
2024-01-26 2:12 dpdklab
2024-01-26 2:12 dpdklab
2024-01-26 2:11 dpdklab
2024-01-26 2:11 dpdklab
2024-01-26 2:10 dpdklab
2024-01-26 2:10 dpdklab
2024-01-26 2:09 dpdklab
2024-01-26 2:08 dpdklab
2024-01-26 2:08 dpdklab
2024-01-26 2:08 dpdklab
2024-01-26 2:07 dpdklab
2024-01-26 2:07 dpdklab
2024-01-26 2:07 dpdklab
2024-01-26 2:07 dpdklab
2024-01-26 2:07 dpdklab
2024-01-26 2:07 dpdklab
2024-01-26 2:06 dpdklab
2024-01-26 2:06 dpdklab
2024-01-26 2:05 dpdklab
2024-01-26 2:05 dpdklab
2024-01-26 2:05 dpdklab
2024-01-26 2:04 dpdklab
2024-01-26 2:04 dpdklab
2024-01-26 2:04 dpdklab
2024-01-26 2:03 dpdklab
2024-01-26 2:03 dpdklab
2024-01-26 2:03 dpdklab
2024-01-26 2:02 dpdklab
2024-01-26 2:02 dpdklab
2024-01-26 2:02 dpdklab
2024-01-26 2:02 dpdklab
2024-01-26 2:01 dpdklab
2024-01-26 2:01 dpdklab
2024-01-26 2:01 dpdklab
2024-01-26 2:00 dpdklab
2024-01-26 2:00 dpdklab
2024-01-26 1:59 dpdklab
2024-01-26 1:59 dpdklab
2024-01-26 1:58 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=65b5bb27.810a0220.2bfce.58efSMTPIN_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).