From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] c66daa12e76d7b4912cfb7109a761856a7a873ab
Date: Sun, 22 Dec 2024 22:45:23 -0800 (PST) [thread overview]
Message-ID: <67690703.250a0220.c838b.0c8cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: tags/v23.11
c66daa12e76d7b4912cfb7109a761856a7a873ab --> testing pass
Upstream job id: ACVP-FIPS-testing#8368
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | PASS |
+--------------------+----------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/32018/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-23 6:45 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 6:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-23 8:30 dpdklab
2024-12-23 6:46 dpdklab
2024-12-23 6:40 dpdklab
2024-12-23 6:40 dpdklab
2024-12-23 6:05 dpdklab
2024-12-23 6:05 dpdklab
2024-12-23 6:05 dpdklab
2024-12-23 6:01 dpdklab
2024-12-23 5:51 dpdklab
2024-12-23 5:39 dpdklab
2024-12-22 8:18 dpdklab
2024-12-22 7:59 dpdklab
2024-12-22 6:43 dpdklab
2024-12-22 6:27 dpdklab
2024-12-22 6:20 dpdklab
2024-12-22 5:46 dpdklab
2024-12-22 5:37 dpdklab
2024-12-22 5:34 dpdklab
2024-12-22 5:31 dpdklab
2024-12-22 5:21 dpdklab
2024-12-22 5:17 dpdklab
2024-12-21 9:31 dpdklab
2024-12-21 7:15 dpdklab
2024-12-21 7:10 dpdklab
2024-12-21 7:07 dpdklab
2024-12-21 6:52 dpdklab
2024-12-21 6:32 dpdklab
2024-12-21 6:32 dpdklab
2024-12-21 5:58 dpdklab
2024-12-21 5:53 dpdklab
2024-12-21 5:42 dpdklab
2024-12-21 5:37 dpdklab
2024-12-21 5:35 dpdklab
2024-12-21 5:30 dpdklab
2024-12-21 5:23 dpdklab
2024-12-21 5:22 dpdklab
2024-12-20 8:59 dpdklab
2024-12-20 8:24 dpdklab
2024-12-20 8:17 dpdklab
2024-12-20 7:59 dpdklab
2024-12-20 7:37 dpdklab
2024-12-20 7:05 dpdklab
2024-12-20 7:04 dpdklab
2024-12-20 6:52 dpdklab
2024-12-20 6:46 dpdklab
2024-12-20 6:38 dpdklab
2024-12-20 6:37 dpdklab
2024-12-20 6:19 dpdklab
2024-12-20 6:12 dpdklab
2024-12-20 6:10 dpdklab
2024-12-20 6:01 dpdklab
2024-12-20 6:00 dpdklab
2024-12-20 5:54 dpdklab
2024-12-19 8:59 dpdklab
2024-12-19 8:26 dpdklab
2024-12-19 8:09 dpdklab
2024-12-19 7:54 dpdklab
2024-12-19 7:38 dpdklab
2024-12-19 7:37 dpdklab
2024-12-19 7:24 dpdklab
2024-12-19 7:12 dpdklab
2024-12-19 7:01 dpdklab
2024-12-19 6:53 dpdklab
2024-12-19 6:45 dpdklab
2024-12-19 6:44 dpdklab
2024-12-19 6:40 dpdklab
2024-12-19 6:35 dpdklab
2024-12-19 6:04 dpdklab
2024-12-19 6:04 dpdklab
2024-12-18 11:07 dpdklab
2024-12-18 10:24 dpdklab
2024-12-18 9:01 dpdklab
2024-12-18 8:55 dpdklab
2024-12-18 8:51 dpdklab
2024-12-18 8:23 dpdklab
2024-12-18 8:13 dpdklab
2024-12-18 8:11 dpdklab
2024-12-18 8:04 dpdklab
2024-12-18 7: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=67690703.250a0220.c838b.0c8cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).