From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152624-152626 [PATCH] [v2,3/3] net/ixgbe: support MDD on
Date: Thu, 27 Mar 2025 12:50:44 -0700 (PDT) [thread overview]
Message-ID: <67e5ac14.050a0220.23ebd5.17ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <d30294bcc7a2d1a59ab623857003f997ad6bccef.1743088329.git.anatoly.burakov@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/152626
_Testing PASS_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Thursday, March 27 2025 15:12:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:edd3f4b1265e6da707c46ca9b6c39d332647baea
152624-152626 --> testing pass
Upstream job id: Template-DTS-Pipeline#219351
Test environment and result as below:
+--------------------+----------------------+
| Environment | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS |
+--------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
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/32904/
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-03-27 19:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d30294bcc7a2d1a59ab623857003f997ad6bccef.1743088329.git.anatoly.burakov@intel.com>
2025-03-27 14:39 ` |SUCCESS| pw152624-152626 [PATCH v2 3/3] net/ixgbe: support MDD on VF Tx path qemudev
2025-03-27 14:43 ` qemudev
2025-03-27 15:12 ` |SUCCESS| pw152626 " checkpatch
2025-03-27 16:23 ` 0-day Robot
2025-03-27 19:21 ` |SUCCESS| pw152624-152626 [PATCH] [v2,3/3] net/ixgbe: support MDD on dpdklab
2025-03-27 19:39 ` dpdklab
2025-03-27 19:50 ` dpdklab [this message]
2025-03-27 19:56 ` dpdklab
2025-03-27 19:58 ` dpdklab
2025-03-27 20:05 ` dpdklab
2025-03-27 20:16 ` dpdklab
2025-03-27 20:50 ` dpdklab
2025-03-27 21:04 ` dpdklab
2025-03-27 21:27 ` dpdklab
2025-03-27 21:27 ` dpdklab
2025-03-27 21:33 ` dpdklab
2025-03-27 21:33 ` dpdklab
2025-03-27 21:39 ` dpdklab
2025-03-27 21:40 ` dpdklab
2025-03-27 21:43 ` dpdklab
2025-03-27 21:51 ` dpdklab
2025-03-27 22:27 ` dpdklab
2025-03-27 22:50 ` |PENDING| " dpdklab
2025-03-27 22:55 ` |SUCCESS| " dpdklab
2025-03-27 23:04 ` dpdklab
2025-03-27 23:09 ` dpdklab
2025-03-27 23:28 ` dpdklab
2025-03-27 23:41 ` dpdklab
2025-03-27 23:56 ` |PENDING| " dpdklab
2025-03-28 0:04 ` |SUCCESS| " dpdklab
2025-03-28 0:20 ` dpdklab
2025-03-28 0:27 ` dpdklab
2025-03-28 0:28 ` dpdklab
2025-03-28 0:43 ` dpdklab
2025-03-28 0:44 ` dpdklab
2025-03-28 1:07 ` dpdklab
2025-03-28 1:12 ` dpdklab
2025-03-28 1:40 ` dpdklab
2025-03-28 1:56 ` dpdklab
2025-03-28 1:58 ` dpdklab
2025-03-28 2:02 ` dpdklab
2025-03-28 2:04 ` dpdklab
2025-03-28 2:05 ` dpdklab
2025-03-28 2:37 ` dpdklab
2025-03-28 20:54 ` dpdklab
2025-03-28 20:58 ` dpdklab
2025-03-29 5:18 ` dpdklab
2025-03-29 5:46 ` 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=67e5ac14.050a0220.23ebd5.17ebSMTPIN_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).