From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw151218 [PATCH] net/mlx5: fix packet hardware ptype trans
Date: Sun, 09 Feb 2025 13:21:43 -0800 (PST) [thread overview]
Message-ID: <67a91c67.050a0220.92ceb.4a0eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250209140106.264556-1-getelson@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/151218
_Testing issues_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sunday, February 09 2025 14:01:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:af389f2da68c0e9bb08a68055996bececbd45108
151218 --> testing issues
Upstream job id: ACVP-FIPS-testing#8855
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 2881071
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 2881072
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 2881073
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/32540/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-02-09 21:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250209140106.264556-1-getelson@nvidia.com>
2025-02-09 13:32 ` |SUCCESS| pw151218 [PATCH] net/mlx5: fix packet hardware ptype translation qemudev
2025-02-09 13:37 ` qemudev
2025-02-09 14:01 ` checkpatch
2025-02-09 15:05 ` 0-day Robot
2025-02-09 19:32 ` |SUCCESS| pw151218 [PATCH] net/mlx5: fix packet hardware ptype trans dpdklab
2025-02-09 19:33 ` |PENDING| " dpdklab
2025-02-09 19:36 ` |SUCCESS| " dpdklab
2025-02-09 19:41 ` dpdklab
2025-02-09 19:41 ` dpdklab
2025-02-09 19:42 ` dpdklab
2025-02-09 19:46 ` dpdklab
2025-02-09 19:48 ` dpdklab
2025-02-09 19:53 ` |PENDING| " dpdklab
2025-02-09 19:55 ` |SUCCESS| " dpdklab
2025-02-09 20:08 ` dpdklab
2025-02-09 20:09 ` |PENDING| " dpdklab
2025-02-09 20:10 ` dpdklab
2025-02-09 20:44 ` |SUCCESS| " dpdklab
2025-02-09 20:48 ` dpdklab
2025-02-09 21:12 ` dpdklab
2025-02-09 21:21 ` dpdklab [this message]
2025-02-09 21:46 ` dpdklab
2025-02-09 22:48 ` 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=67a91c67.050a0220.92ceb.4a0eSMTPIN_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).