From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw157202-157204 [PATCH] [v4,3/3] dts: add performance test
Date: Wed, 01 Oct 2025 20:14:26 -0700 (PDT) [thread overview]
Message-ID: <68ddee12.5d0a0220.93bbf.3e7fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251001231659.2297751-4-probb@iol.unh.edu>
Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/157204
_Testing issues_
Submitter: Patrick Robb <probb@iol.unh.edu>
Date: Wednesday, October 01 2025 23:16:59
DPDK git baseline: Repo:dpdk-next-dts
Branch: master
CommitID:b71d7bdf2b663f9fedc1d344b81a8cf65518026c
157202-157204 --> testing issues
Upstream job id: ACVP-FIPS-testing#11296
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | WARN | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
INFO:root:Downloading verdict for vector set 3416478
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 3416479
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 3416684
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
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34197/
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-10-02 3:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251001231659.2297751-4-probb@iol.unh.edu>
2025-10-01 23:21 ` |SUCCESS| pw157204 [PATCH v4 3/3] dts: add performance test functions to test suite API checkpatch
2025-10-01 23:37 ` |FAILURE| pw157202-157204 [PATCH] [v4,3/3] dts: add performance test dpdklab
2025-10-01 23:39 ` |PENDING| " dpdklab
2025-10-01 23:52 ` dpdklab
2025-10-01 23:53 ` dpdklab
2025-10-01 23:53 ` |SUCCESS| " dpdklab
2025-10-01 23:54 ` dpdklab
2025-10-01 23:59 ` |PENDING| " dpdklab
2025-10-02 0:06 ` |SUCCESS| " dpdklab
2025-10-02 0:11 ` |FAILURE| " dpdklab
2025-10-02 0:12 ` dpdklab
2025-10-02 0:12 ` |SUCCESS| " dpdklab
2025-10-02 0:24 ` |FAILURE| " dpdklab
2025-10-02 0:42 ` |SUCCESS| " dpdklab
2025-10-02 0:48 ` dpdklab
2025-10-02 3:14 ` 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=68ddee12.5d0a0220.93bbf.3e7fSMTPIN_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).