From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154970-154973 [PATCH] [v3,4/4] dts: add sr-iov section t
Date: Wed, 02 Jul 2025 14:20:46 -0700 (PDT) [thread overview]
Message-ID: <6865a2ae.170a0220.73f11.19faSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250702162331.352313-4-dmarx@iol.unh.edu>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/154973
_Testing PASS_
Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Wednesday, July 02 2025 16:23:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:47b315bcb2778bcbd76c5764a5ed891b93b05814
154970-154973 --> testing pass
Upstream job id: Template-DTS-Pipeline#234644
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) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33571/
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-02 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250702162331.352313-4-dmarx@iol.unh.edu>
2025-07-02 16:22 ` |SUCCESS| pw154973 [PATCH v3 4/4] dts: add sr-iov section to docs checkpatch
2025-07-02 19:10 ` |SUCCESS| pw154970-154973 [PATCH] [v3,4/4] dts: add sr-iov section t dpdklab
2025-07-02 19:44 ` dpdklab
2025-07-02 19:45 ` |PENDING| " dpdklab
2025-07-02 19:51 ` |SUCCESS| " dpdklab
2025-07-02 20:29 ` |PENDING| " dpdklab
2025-07-02 21:20 ` dpdklab [this message]
2025-07-02 21:27 ` |SUCCESS| " dpdklab
2025-07-03 0:34 ` |FAILURE| " dpdklab
2025-07-03 0:47 ` |PENDING| " 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=6865a2ae.170a0220.73f11.19faSMTPIN_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).