From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155086 [PATCH] net/mlx5: fix the queue length checking
Date: Wed, 09 Jul 2025 00:09:17 -0700 (PDT) [thread overview]
Message-ID: <686e159d.050a0220.1ab954.71b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250709040000.112338-1-bingz@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/155086
_Functional Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Wednesday, July 09 2025 04:00:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2888614268cbf0abcc7cd72ad97ff4e4901d0a5
155086 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#235975
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33619/
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-09 7:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250709040000.112338-1-bingz@nvidia.com>
2025-07-09 3:27 ` qemudev
2025-07-09 3:32 ` qemudev
2025-07-09 3:59 ` checkpatch
2025-07-09 5:23 ` 0-day Robot
2025-07-09 7:09 ` dpdklab [this message]
2025-07-09 7:13 ` dpdklab
2025-07-09 9:00 ` dpdklab
2025-07-09 9:28 ` dpdklab
2025-07-09 9:29 ` |PENDING| " dpdklab
2025-07-09 9:34 ` |SUCCESS| " dpdklab
2025-07-09 9:55 ` |PENDING| " dpdklab
2025-07-09 10:11 ` |SUCCESS| " dpdklab
2025-07-09 10:45 ` |PENDING| " dpdklab
2025-07-09 11:33 ` |SUCCESS| " dpdklab
2025-07-09 11:34 ` |PENDING| " dpdklab
2025-07-09 11:50 ` |SUCCESS| " dpdklab
2025-07-09 11:51 ` dpdklab
2025-07-09 11:52 ` dpdklab
2025-07-09 11:54 ` dpdklab
2025-07-09 11:54 ` dpdklab
2025-07-09 11:55 ` dpdklab
2025-07-09 12:49 ` dpdklab
2025-07-09 12:50 ` |WARNING| " dpdklab
2025-07-09 12:50 ` dpdklab
2025-07-09 12:51 ` dpdklab
2025-07-09 12:51 ` dpdklab
2025-07-09 12:52 ` dpdklab
2025-07-09 13:12 ` dpdklab
2025-07-09 13:18 ` dpdklab
2025-07-09 14:11 ` dpdklab
2025-07-09 15:07 ` |SUCCESS| " dpdklab
2025-07-09 15:07 ` dpdklab
2025-07-09 16:17 ` 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=686e159d.050a0220.1ab954.71b6SMTPIN_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).