From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw158776 [PATCH] app/testpmd: fix flex item link parsing
Date: Thu, 13 Nov 2025 14:11:49 -0800 (PST) [thread overview]
Message-ID: <691657a5.170a0220.607dc.0fe5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251113201726.10597-1-mkashani@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/158776
_Testing PASS_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Thursday, November 13 2025 20:17:25
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:fca6f2910345c25a5050a0b586e0d324ca616cbb
158776 --> testing pass
Upstream job id: Template-DTS-Pipeline#254768
Test environment and result as below:
+--------------+----------------------+
| Environment | compressdev_zlib_pmd |
+==============+======================+
| Ubuntu 22.04 | PASS |
+--------------+----------------------+
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/34583/
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-13 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251113201726.10597-1-mkashani@nvidia.com>
2025-11-13 19:43 ` qemudev
2025-11-13 19:48 ` qemudev
2025-11-13 20:18 ` checkpatch
2025-11-13 21:19 ` 0-day Robot
2025-11-13 21:19 ` 0-day Robot
2025-11-13 21:59 ` |PENDING| " dpdklab
2025-11-13 22:03 ` |SUCCESS| " dpdklab
2025-11-13 22:03 ` dpdklab
2025-11-13 22:07 ` |PENDING| " dpdklab
2025-11-13 22:07 ` |SUCCESS| " dpdklab
2025-11-13 22:09 ` |PENDING| " dpdklab
2025-11-13 22:11 ` dpdklab [this message]
2025-11-13 22:42 ` |SUCCESS| " dpdklab
2025-11-13 22:51 ` dpdklab
2025-11-13 23:41 ` 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=691657a5.170a0220.607dc.0fe5SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).