From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] a63c6426fdfd9233ba9c7d4503e52bff3732fe69
Date: Sat, 09 Nov 2024 18:27:29 -0800 (PST) [thread overview]
Message-ID: <67301a11.d40a0220.2a59e9.77f0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
a63c6426fdfd9233ba9c7d4503e52bff3732fe69 --> testing pass
Upstream job id: ACVP-FIPS-testing#7859
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+====================+======================+======================+
| Ubuntu 20.04 | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 (ARM) | SKIPPED | PASS |
+--------------------+----------------------+----------------------+
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31493/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-11-10 2:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 2:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-10 4:38 dpdklab
2024-11-10 3:26 dpdklab
2024-11-10 2:47 dpdklab
2024-11-10 2:32 dpdklab
2024-11-10 2:24 dpdklab
2024-11-10 2:17 dpdklab
2024-11-10 1:57 dpdklab
2024-11-10 1:50 dpdklab
2024-11-10 1:48 dpdklab
2024-11-10 1:43 dpdklab
2024-11-10 1:41 dpdklab
2024-11-10 1:40 dpdklab
2024-11-10 1: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=67301a11.d40a0220.2a59e9.77f0SMTPIN_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).