From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw155545-155557 [PATCH] [v12,13/13] net/sxe: add virtual f
Date: Mon, 28 Jul 2025 12:59:25 -0700 (PDT) [thread overview]
Message-ID: <6887d69d.c80a0220.24e233.6b0dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250728090517.1811244-13-liujie5@linkdatatechnology.com>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/155557
_Testing issues_
Submitter: Jie Liu <liujie5@linkdatatechnology.com>
Date: Monday, July 28 2025 09:05:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:38543d33bd47fc0ee21f59db80a8763620741879
155545-155557 --> testing issues
Upstream job id: ACVP-FIPS-testing#10628
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | WARN |
+--------------+----------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
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 3264565
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: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: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: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 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33758/
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-07-28 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250728090517.1811244-13-liujie5@linkdatatechnology.com>
2025-07-28 8:36 ` |SUCCESS| pw155545-155557 [PATCH v12 13/13] net/sxe: add virtual function qemudev
2025-07-28 8:40 ` qemudev
2025-07-28 9:09 ` |WARNING| pw155557 " checkpatch
2025-07-28 10:24 ` |SUCCESS| " 0-day Robot
2025-07-28 16:14 ` |PENDING| pw155545-155557 [PATCH] [v12,13/13] net/sxe: add virtual f dpdklab
2025-07-28 16:17 ` dpdklab
2025-07-28 16:46 ` |SUCCESS| " dpdklab
2025-07-28 17:14 ` dpdklab
2025-07-28 17:26 ` dpdklab
2025-07-28 18:02 ` dpdklab
2025-07-28 18:35 ` |PENDING| " dpdklab
2025-07-28 19:59 ` dpdklab [this message]
2025-07-29 0:06 ` |SUCCESS| " dpdklab
2025-07-29 0:08 ` 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=6887d69d.c80a0220.24e233.6b0dSMTPIN_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).