From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] abb4cc0efc1b0f7779bbe3e24bcb362146351c6e
Date: Fri, 09 Jun 2023 20:43:09 -0700 (PDT) [thread overview]
Message-ID: <6483f14d.050a0220.e9b64.b532SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
abb4cc0efc1b0f7779bbe3e24bcb362146351c6e --> 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/24939/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-10 3:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 3:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-11 9:07 dpdklab
2023-06-10 3:59 dpdklab
2023-06-10 3:47 dpdklab
2023-06-10 3:21 dpdklab
2023-06-10 3:20 dpdklab
2023-06-10 3:12 dpdklab
2023-06-10 3:04 dpdklab
2023-06-10 2:52 dpdklab
2023-06-10 2:42 dpdklab
2023-06-10 2:42 dpdklab
2023-06-10 2:38 dpdklab
2023-06-10 2:38 dpdklab
2023-06-10 2:38 dpdklab
2023-06-10 2:26 dpdklab
2023-06-10 2:24 dpdklab
2023-06-10 2:16 dpdklab
2023-06-10 2:14 dpdklab
2023-06-10 2:12 dpdklab
2023-06-10 2:12 dpdklab
2023-06-10 2:06 dpdklab
2023-06-10 1:29 dpdklab
2023-06-10 1:19 dpdklab
2023-06-10 1:14 dpdklab
2023-06-10 1:13 dpdklab
2023-06-10 1:12 dpdklab
2023-06-10 1:10 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=6483f14d.050a0220.e9b64.b532SMTPIN_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).