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] 39bcde2d05afc0f904f906182be1e659b60ceeb7
Date: Wed, 18 Dec 2024 05:53:19 -0800 (PST) [thread overview]
Message-ID: <6762d3cf.d40a0220.26cd20.f2e2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: 23.11-staging
39bcde2d05afc0f904f906182be1e659b60ceeb7 --> testing pass
Upstream job id: ACVP-FIPS-testing#8318
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/31961/
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-18 13:53 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 13:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-19 1:10 dpdklab
2024-12-19 0:36 dpdklab
2024-12-19 0:35 dpdklab
2024-12-18 12:11 dpdklab
2024-12-18 4:58 dpdklab
2024-12-18 4:31 dpdklab
2024-12-18 4:30 dpdklab
2024-12-18 4:30 dpdklab
2024-12-18 4:01 dpdklab
2024-12-18 3:43 dpdklab
2024-12-18 1:58 dpdklab
2024-12-18 1:50 dpdklab
2024-12-18 1:39 dpdklab
2024-12-18 1:19 dpdklab
2024-12-18 1:01 dpdklab
2024-12-18 0:57 dpdklab
2024-12-18 0:56 dpdklab
2024-12-18 0:05 dpdklab
2024-12-17 23:52 dpdklab
2024-12-17 10:53 dpdklab
2024-12-17 9:49 dpdklab
2024-12-17 7:55 dpdklab
2024-12-17 7:48 dpdklab
2024-12-17 7:34 dpdklab
2024-12-17 7:12 dpdklab
2024-12-17 7:07 dpdklab
2024-12-17 6:30 dpdklab
2024-12-17 6:27 dpdklab
2024-12-17 6:26 dpdklab
2024-12-17 6:26 dpdklab
2024-12-17 6:25 dpdklab
2024-12-17 5:51 dpdklab
2024-12-17 5:46 dpdklab
2024-12-17 5:39 dpdklab
2024-12-17 5:36 dpdklab
2024-12-15 8:41 dpdklab
2024-12-15 8:03 dpdklab
2024-12-15 7:18 dpdklab
2024-12-15 7:16 dpdklab
2024-12-15 7:12 dpdklab
2024-12-15 7:00 dpdklab
2024-12-15 6:30 dpdklab
2024-12-15 6:10 dpdklab
2024-12-15 6:03 dpdklab
2024-12-15 5:58 dpdklab
2024-12-15 5:48 dpdklab
2024-12-15 5:45 dpdklab
2024-12-15 5:41 dpdklab
2024-12-15 5:38 dpdklab
2024-12-15 5:38 dpdklab
2024-12-15 5:28 dpdklab
2024-12-15 5:27 dpdklab
2024-12-15 5:23 dpdklab
2024-12-14 5:42 dpdklab
2024-12-14 3:47 dpdklab
2024-12-14 1:26 dpdklab
2024-12-14 0:57 dpdklab
2024-12-14 0:48 dpdklab
2024-12-14 0:05 dpdklab
2024-12-14 0:00 dpdklab
2024-12-13 17:21 dpdklab
2024-12-13 17:10 dpdklab
2024-12-13 16:55 dpdklab
2024-12-13 16:48 dpdklab
2024-12-13 16:45 dpdklab
2024-12-13 16:44 dpdklab
2024-12-13 16:37 dpdklab
2024-12-13 16:30 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=6762d3cf.d40a0220.26cd20.f2e2SMTPIN_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).