From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Qi Zhang <qi.z.zhang@intel.com>
Subject: |SUCCESS| [GIT MASTER] 9f22ded48628e289e52b186780d741ee5bfef419
Date: Thu, 04 Jan 2024 06:13:17 -0800 (PST) [thread overview]
Message-ID: <6596bcfd.250a0220.34fa.1f48SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
9f22ded48628e289e52b186780d741ee5bfef419 --> 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/27543/
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-04 14:13 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 14:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 23:47 dpdklab
2024-01-04 23:37 dpdklab
2024-01-04 22:55 dpdklab
2024-01-04 22:46 dpdklab
2024-01-04 10:45 dpdklab
2024-01-04 5:45 dpdklab
2024-01-04 2:33 dpdklab
2024-01-04 2:27 dpdklab
2024-01-04 2:27 dpdklab
2024-01-04 1:28 dpdklab
2024-01-04 1:26 dpdklab
2024-01-04 1:23 dpdklab
2024-01-04 1:22 dpdklab
2024-01-04 1:22 dpdklab
2024-01-04 1:20 dpdklab
2024-01-04 1:18 dpdklab
2024-01-04 1:18 dpdklab
2024-01-04 1:17 dpdklab
2024-01-04 1:14 dpdklab
2024-01-04 1:14 dpdklab
2024-01-04 1:14 dpdklab
2024-01-04 1:14 dpdklab
2024-01-04 1:14 dpdklab
2024-01-04 1:14 dpdklab
2024-01-04 1:13 dpdklab
2024-01-04 1:12 dpdklab
2024-01-04 1:12 dpdklab
2024-01-04 1:12 dpdklab
2024-01-04 1:11 dpdklab
2024-01-04 1:10 dpdklab
2024-01-04 1:10 dpdklab
2024-01-04 1:10 dpdklab
2024-01-04 1:09 dpdklab
2024-01-04 1:08 dpdklab
2024-01-04 1:08 dpdklab
2024-01-04 1:08 dpdklab
2024-01-04 1:08 dpdklab
2024-01-04 1:08 dpdklab
2024-01-04 1:06 dpdklab
2024-01-04 1:06 dpdklab
2024-01-04 1:06 dpdklab
2024-01-04 1:05 dpdklab
2024-01-04 1:05 dpdklab
2024-01-04 1:05 dpdklab
2024-01-04 1:04 dpdklab
2024-01-04 1:04 dpdklab
2024-01-04 1:03 dpdklab
2024-01-04 1:03 dpdklab
2024-01-04 1:01 dpdklab
2024-01-04 1:00 dpdklab
2024-01-04 1:00 dpdklab
2024-01-04 1:00 dpdklab
2024-01-04 0:59 dpdklab
2024-01-04 0:59 dpdklab
2024-01-04 0:58 dpdklab
2024-01-04 0:57 dpdklab
2024-01-04 0:57 dpdklab
2024-01-04 0:56 dpdklab
2024-01-04 0:56 dpdklab
2024-01-04 0:55 dpdklab
2024-01-04 0:51 dpdklab
2024-01-04 0:49 dpdklab
2024-01-04 0:39 dpdklab
2024-01-04 0:31 dpdklab
2024-01-04 0:31 dpdklab
2024-01-04 0:31 dpdklab
2024-01-04 0:27 dpdklab
2024-01-04 0:27 dpdklab
2024-01-04 0:23 dpdklab
2024-01-04 0:23 dpdklab
2024-01-04 0:22 dpdklab
2024-01-04 0:22 dpdklab
2024-01-04 0:21 dpdklab
2024-01-04 0:20 dpdklab
2024-01-04 0:20 dpdklab
2024-01-04 0:20 dpdklab
2024-01-04 0:12 dpdklab
2024-01-04 0:10 dpdklab
2024-01-04 0:10 dpdklab
2024-01-04 0:04 dpdklab
2024-01-04 0:03 dpdklab
2024-01-03 23:59 dpdklab
2024-01-03 23:58 dpdklab
2024-01-03 23:58 dpdklab
2024-01-03 23:57 dpdklab
2024-01-03 23:56 dpdklab
2024-01-03 23:54 dpdklab
2024-01-03 23:53 dpdklab
2024-01-03 23:44 dpdklab
2024-01-03 23:37 dpdklab
2024-01-03 23:37 dpdklab
2024-01-03 23:36 dpdklab
2024-01-03 23:36 dpdklab
2024-01-03 23:35 dpdklab
2024-01-03 23:35 dpdklab
2024-01-03 23:29 dpdklab
2024-01-03 23:25 dpdklab
2024-01-03 23:24 dpdklab
2024-01-03 23:23 dpdklab
2024-01-03 23:04 dpdklab
2024-01-03 23:00 dpdklab
2024-01-03 22:58 dpdklab
2024-01-03 22:56 dpdklab
2024-01-03 22:54 dpdklab
2024-01-03 22:53 dpdklab
2024-01-03 22:52 dpdklab
2024-01-03 22:50 dpdklab
2024-01-03 22:44 dpdklab
2024-01-03 22:41 dpdklab
2024-01-03 22:40 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=6596bcfd.250a0220.34fa.1f48SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=qi.z.zhang@intel.com \
--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).