automatic DPDK test reports
 help / color / mirror / Atom feed
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] f2eea2f37a82bb73fb01d56350708f7d70e21379
Date: Fri, 07 Feb 2025 15:05:02 -0800 (PST)	[thread overview]
Message-ID: <67a6919e.050a0220.1ee672.fa12SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v24.11

f2eea2f37a82bb73fb01d56350708f7d70e21379 --> testing issues

Upstream job id: ACVP-FIPS-testing#8806

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:Using response file...
Traceback (most recent call last):
File "/dpdk-ci/tools/acvp/acvp_tool.py", line 368, in <module>
main(
File "/dpdk-ci/tools/acvp/acvp_tool.py", line 314, in main
with open(response_path, 'r') as upload_file:
FileNotFoundError: [Errno 2] No such file or directory: '/home-local/jenkins-local/jenkins-agent/workspace/ACVP-FIPS-testing/out/hmac-sha-1-answers.rsp'
INFO:root:Using response file...
INFO:root:Uploading response file...
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 2878361
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 2878364
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/32466/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2025-02-07 23:05 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 23:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-07 19:06 dpdklab
2025-02-07 19:05 dpdklab
2025-02-07 19:05 dpdklab
2025-02-07 18:13 dpdklab
2025-02-07 18:13 dpdklab
2025-02-07 18:11 dpdklab
2025-02-07 18:11 dpdklab
2025-02-07 18:10 dpdklab
2025-02-07 18:10 dpdklab
2025-02-07 18:09 dpdklab
2025-02-07 18:00 dpdklab
2025-02-07 17:53 dpdklab
2025-02-05 13:57 dpdklab
2025-02-05 10:53 dpdklab
2025-02-05 10:43 dpdklab
2025-02-05 10:13 dpdklab
2025-02-05  8:33 dpdklab
2025-02-05  7:16 dpdklab
2025-02-05  4:48 dpdklab
2025-02-05  3:45 dpdklab
2025-02-05  2:19 dpdklab
2025-02-05  2:02 dpdklab
2025-02-05  1:46 dpdklab
2025-02-03  8:20 dpdklab
2025-02-02  8:17 dpdklab
2025-02-01  9:24 dpdklab
2025-01-31  9:05 dpdklab
2025-01-30  9:26 dpdklab
2025-01-29  9:00 dpdklab
2025-01-29  9:00 dpdklab
2025-01-28 10:24 dpdklab
2025-01-27 21:39 dpdklab
2025-01-27  9:32 dpdklab
2025-01-26  8:19 dpdklab
2025-01-25 13:38 dpdklab
2025-01-25 13:10 dpdklab
2025-01-25 13:10 dpdklab
2025-01-25 13:09 dpdklab
2025-01-24  8:59 dpdklab
2025-01-23  7:41 dpdklab
2025-01-22  9:56 dpdklab
2025-01-20  9:44 dpdklab
2025-01-19  8:39 dpdklab
2025-01-18  9:12 dpdklab
2025-01-17  8:13 dpdklab
2025-01-16  9:25 dpdklab
2025-01-15 10:08 dpdklab
2025-01-14  7:22 dpdklab
2025-01-13  8:27 dpdklab
2025-01-12  8:05 dpdklab
2025-01-11  7:33 dpdklab
2025-01-10  8:29 dpdklab
2025-01-08  2:39 dpdklab
2025-01-08  2:33 dpdklab
2025-01-08  2:31 dpdklab
2025-01-08  2:28 dpdklab
2025-01-08  2:28 dpdklab
2025-01-08  2:24 dpdklab
2025-01-08  2:19 dpdklab
2025-01-06  8:30 dpdklab
2025-01-05  8:26 dpdklab
2025-01-04  7:57 dpdklab
2025-01-03 11:17 dpdklab
2025-01-03 10:47 dpdklab
2025-01-03  9:24 dpdklab
2024-12-31  7:53 dpdklab
2024-12-30  8:04 dpdklab
2024-12-30  7:12 dpdklab
2024-12-29  7:46 dpdklab
2024-12-29  7:12 dpdklab
2024-12-27  7:45 dpdklab
2024-12-27  7:17 dpdklab
2024-12-26  8:19 dpdklab
2024-12-26  8:18 dpdklab
2024-12-25  7:03 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=67a6919e.050a0220.1ee672.fa12SMTPIN_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).