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: |WARNING| [GIT MASTER] c66daa12e76d7b4912cfb7109a761856a7a873ab
Date: Fri, 07 Feb 2025 18:47:19 -0800 (PST) [thread overview]
Message-ID: <67a6c5b7.050a0220.260a94.a13aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: tags/v23.11
c66daa12e76d7b4912cfb7109a761856a7a873ab --> testing issues
Upstream job id: ACVP-FIPS-testing#8807
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 | WARN |
+--------------------+----------------------+----------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
INFO:root:Downloading verdict for vector set 2879183
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
INFO:root:Using response file...
INFO:root:Uploading response file...
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 2879184
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
INFO:root:Using response file...
INFO:root:Uploading response file...
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 2879185
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
==== End log output ====
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/32467/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-02-08 2:47 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 2:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 19:06 dpdklab
2025-02-07 19:06 dpdklab
2025-02-07 19:05 dpdklab
2025-02-07 19:05 dpdklab
2025-02-07 18:20 dpdklab
2025-02-07 18:20 dpdklab
2025-02-07 18:19 dpdklab
2025-02-07 18:18 dpdklab
2025-02-07 18:13 dpdklab
2025-02-07 18:13 dpdklab
2025-02-07 18:13 dpdklab
2025-02-07 18:11 dpdklab
2025-02-07 18:10 dpdklab
2025-02-07 18:10 dpdklab
2025-02-07 17:57 dpdklab
2025-02-07 17:55 dpdklab
2025-02-07 17:53 dpdklab
2025-02-05 13:52 dpdklab
2025-02-05 11:01 dpdklab
2025-02-05 10:38 dpdklab
2025-02-05 10:19 dpdklab
2025-02-05 8:38 dpdklab
2025-02-05 7:00 dpdklab
2025-02-05 4:44 dpdklab
2025-02-05 3:39 dpdklab
2025-02-05 2:24 dpdklab
2025-02-05 1:56 dpdklab
2025-02-05 1:39 dpdklab
2025-02-03 9:06 dpdklab
2025-02-03 8:58 dpdklab
2025-02-03 8:55 dpdklab
2025-02-02 8:48 dpdklab
2025-02-01 9:25 dpdklab
2025-01-31 11:11 dpdklab
2025-01-31 10:36 dpdklab
2025-01-31 10:35 dpdklab
2025-01-31 10:27 dpdklab
2025-01-31 10:18 dpdklab
2025-01-31 10:14 dpdklab
2025-01-31 10:12 dpdklab
2025-01-30 9:10 dpdklab
2025-01-29 9:34 dpdklab
2025-01-27 13:25 dpdklab
2025-01-27 8:37 dpdklab
2025-01-26 8:49 dpdklab
2025-01-25 12:19 dpdklab
2025-01-25 11:29 dpdklab
2025-01-25 11:24 dpdklab
2025-01-25 11:21 dpdklab
2025-01-24 8:42 dpdklab
2025-01-23 9:28 dpdklab
2025-01-22 9:01 dpdklab
2025-01-20 9:14 dpdklab
2025-01-19 8:12 dpdklab
2025-01-18 8:57 dpdklab
2025-01-17 9:03 dpdklab
2025-01-17 9:01 dpdklab
2025-01-16 9:28 dpdklab
2025-01-15 9:03 dpdklab
2025-01-15 9:01 dpdklab
2025-01-14 10:05 dpdklab
2025-01-13 8:13 dpdklab
2025-01-12 7:53 dpdklab
2025-01-11 8:46 dpdklab
2025-01-10 8:33 dpdklab
2025-01-10 8:33 dpdklab
2025-01-09 20:28 dpdklab
2025-01-09 20:19 dpdklab
2025-01-09 18:08 dpdklab
2025-01-09 14:29 dpdklab
2025-01-06 7:51 dpdklab
2025-01-05 7:57 dpdklab
2025-01-05 7:56 dpdklab
2025-01-04 8:40 dpdklab
2024-12-31 8:19 dpdklab
2024-12-30 8:19 dpdklab
2024-12-29 8:00 dpdklab
2024-12-29 7:36 dpdklab
2024-12-27 8:10 dpdklab
2024-12-27 7:00 dpdklab
2024-12-26 7:58 dpdklab
2024-12-26 7:38 dpdklab
2024-12-25 8:50 dpdklab
2024-12-24 8:40 dpdklab
2024-12-23 8:20 dpdklab
2024-12-22 8:16 dpdklab
2024-12-21 7:55 dpdklab
2024-12-21 7:54 dpdklab
2024-12-20 8:56 dpdklab
2024-12-20 8:55 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=67a6c5b7.050a0220.260a94.a13aSMTPIN_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).