From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw152539-152542 [PATCH] [v3,4/4] net/idpf: use common Tx f
Date: Mon, 24 Mar 2025 12:16:45 -0700 (PDT) [thread overview]
Message-ID: <67e1af9d.0d0a0220.3522d7.19d4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250324124908.1282692-5-shaiq.wani@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/152542
_Testing issues_
Submitter: Shaiq Wani <shaiq.wani@intel.com>
Date: Monday, March 24 2025 12:49:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6b500b1d65a0f9d56479c9c013a5faab643aaea5
152539-152542 --> testing issues
Upstream job id: ACVP-FIPS-testing#9349
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): ====
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 3016716
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 3016743
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/patchsets/32876/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-03-24 19:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250324124908.1282692-5-shaiq.wani@intel.com>
2025-03-24 12:22 ` |SUCCESS| pw152539-152542 [PATCH v3 4/4] net/idpf: use common Tx free fn in idpf qemudev
2025-03-24 12:26 ` qemudev
2025-03-24 12:48 ` |SUCCESS| pw152542 " checkpatch
2025-03-24 14:03 ` 0-day Robot
2025-03-24 15:19 ` |SUCCESS| pw152539-152542 [PATCH] [v3,4/4] net/idpf: use common Tx f dpdklab
2025-03-24 15:31 ` dpdklab
2025-03-24 15:35 ` dpdklab
2025-03-24 15:44 ` dpdklab
2025-03-24 15:45 ` dpdklab
2025-03-24 15:48 ` dpdklab
2025-03-24 15:51 ` dpdklab
2025-03-24 16:00 ` dpdklab
2025-03-24 16:12 ` dpdklab
2025-03-24 16:15 ` dpdklab
2025-03-24 16:22 ` |PENDING| " dpdklab
2025-03-24 16:38 ` dpdklab
2025-03-24 17:08 ` |SUCCESS| " dpdklab
2025-03-24 17:09 ` |PENDING| " dpdklab
2025-03-24 17:12 ` |SUCCESS| " dpdklab
2025-03-24 17:32 ` dpdklab
2025-03-24 17:40 ` dpdklab
2025-03-24 17:49 ` dpdklab
2025-03-24 17:53 ` dpdklab
2025-03-24 18:41 ` dpdklab
2025-03-24 19:16 ` dpdklab [this message]
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=67e1af9d.0d0a0220.3522d7.19d4SMTPIN_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).