From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw158849 [PATCH] test-flow-perf: fix the incorrect array l
Date: Mon, 17 Nov 2025 05:09:48 -0800 (PST) [thread overview]
Message-ID: <691b1e9c.050a0220.3dbc62.f5dcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251117072858.9318-1-bingz@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/158849
_Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, November 17 2025 07:28:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:be0112878b4fc3a1b918370ed2fe615c52039d77
158849 --> testing pass
Upstream job id: ACVP-FIPS-testing#11854
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+==============+======================+======================+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
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/34620/
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-11-17 13:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251117072858.9318-1-bingz@nvidia.com>
2025-11-17 7:30 ` |SUCCESS| pw158849 [PATCH] test-flow-perf: fix the incorrect array length checkpatch
2025-11-17 7:36 ` qemudev
2025-11-17 7:40 ` qemudev
2025-11-17 8:36 ` 0-day Robot
2025-11-17 8:36 ` 0-day Robot
2025-11-17 9:01 ` |PENDING| pw158849 [PATCH] test-flow-perf: fix the incorrect array l dpdklab
2025-11-17 9:02 ` |SUCCESS| " dpdklab
2025-11-17 9:08 ` dpdklab
2025-11-17 9:10 ` dpdklab
2025-11-17 9:13 ` dpdklab
2025-11-17 10:04 ` |PENDING| " dpdklab
2025-11-17 11:54 ` dpdklab
2025-11-17 12:26 ` |SUCCESS| " dpdklab
2025-11-17 13:06 ` dpdklab
2025-11-17 13:09 ` dpdklab [this message]
2025-11-17 13:16 ` dpdklab
2025-11-17 14:14 ` dpdklab
2025-11-17 14:54 ` dpdklab
2025-11-17 14:55 ` dpdklab
2025-11-17 15:05 ` dpdklab
2025-11-17 15:18 ` dpdklab
2025-11-17 17:18 ` dpdklab
2025-11-17 17:31 ` dpdklab
2025-11-17 18:00 ` dpdklab
2025-11-17 18:17 ` dpdklab
2025-11-17 18:54 ` 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=691b1e9c.050a0220.3dbc62.f5dcSMTPIN_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).