From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152861-152864 [PATCH] [v7,4/4] net/idpf: use common Tx f
Date: Thu, 10 Apr 2025 14:30:04 -0700 (PDT) [thread overview]
Message-ID: <67f8385c.170a0220.50ffa.a20dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250410052406.293110-5-shaiq.wani@intel.com>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152864
_Functional Testing PASS_
Submitter: Shaiq Wani <shaiq.wani@intel.com>
Date: Thursday, April 10 2025 05:24:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d7817c378fecd07c59360667f93c25dff4b1a145
152861-152864 --> functional testing pass
Upstream job id: Template-DPDK-DTS-Pipeline#175
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8.0-55-generic
Compiler: gcc 13.3.0
NIC: Mellanox ConnectX-5 100000 Mbps
Aggregate Results by Test Suite
+----------------------------------+--------+
| Test Suite | Result |
+==================================+========+
| TestBlocklist | PASS |
+----------------------------------+--------+
| TestPMDBufferScatter | PASS |
+----------------------------------+--------+
| TestPromiscSupport | PASS |
+----------------------------------+--------+
| TestUniPkt | PASS |
+----------------------------------+--------+
| TestDynamicConfig | PASS |
+----------------------------------+--------+
| TestHelloWorld | PASS |
+----------------------------------+--------+
| TestL2fwd | PASS |
+----------------------------------+--------+
| TestMacFilter | PASS |
+----------------------------------+--------+
| TestMTU | PASS |
+----------------------------------+--------+
| TestPortRestartConfigPersistency | PASS |
+----------------------------------+--------+
| TestSoftNIC | PASS |
+----------------------------------+--------+
| TestVLAN | PASS |
+----------------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32984/
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-04-10 21:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250410052406.293110-5-shaiq.wani@intel.com>
2025-04-10 4:54 ` |SUCCESS| pw152861-152864 [PATCH v7 4/4] net/idpf: use common Tx free fn in idpf qemudev
2025-04-10 4:59 ` qemudev
2025-04-10 5:24 ` |SUCCESS| pw152864 " checkpatch
2025-04-10 6:18 ` |SUCCESS| pw152861-152864 [PATCH] [v7,4/4] net/idpf: use common Tx f dpdklab
2025-04-10 6:19 ` |PENDING| " dpdklab
2025-04-10 6:24 ` |SUCCESS| " dpdklab
2025-04-10 6:25 ` dpdklab
2025-04-10 6:27 ` dpdklab
2025-04-10 6:29 ` dpdklab
2025-04-10 6:42 ` |PENDING| " dpdklab
2025-04-10 6:43 ` |SUCCESS| pw152864 [PATCH v7 4/4] net/idpf: use common Tx free fn in idpf 0-day Robot
2025-04-10 6:45 ` |SUCCESS| pw152861-152864 [PATCH] [v7,4/4] net/idpf: use common Tx f dpdklab
2025-04-10 7:03 ` |PENDING| " dpdklab
2025-04-10 7:10 ` |SUCCESS| " dpdklab
2025-04-10 7:19 ` dpdklab
2025-04-10 7:33 ` dpdklab
2025-04-10 8:20 ` dpdklab
2025-04-10 8:51 ` dpdklab
2025-04-10 8:54 ` dpdklab
2025-04-10 8:57 ` dpdklab
2025-04-10 9:11 ` dpdklab
2025-04-10 10:12 ` dpdklab
2025-04-10 21:30 ` dpdklab
2025-04-10 21:30 ` dpdklab [this message]
2025-04-11 21: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=67f8385c.170a0220.50ffa.a20dSMTPIN_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).