From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152996 [PATCH] [v2] net/ixgbe: support Rx/Tx burst mode
Date: Wed, 16 Apr 2025 18:51:03 -0700 (PDT) [thread overview]
Message-ID: <68005e87.050a0220.31ab6d.8dedSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250416171111.3094521-1-rmelton@cisco.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152996
_Functional Testing PASS_
Submitter: Roger Melton <rmelton@cisco.com>
Date: Wednesday, April 16 2025 17:11:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d7817c378fecd07c59360667f93c25dff4b1a145
152996 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#221966
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33022/
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-17 1:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250416171111.3094521-1-rmelton@cisco.com>
2025-04-16 16:39 ` |SUCCESS| pw152996 [PATCH v2] net/ixgbe: support Rx/Tx burst mode info qemudev
2025-04-16 16:44 ` qemudev
2025-04-16 17:13 ` |WARNING| " checkpatch
2025-04-17 1:29 ` |SUCCESS| pw152996 [PATCH] [v2] net/ixgbe: support Rx/Tx burst mode dpdklab
2025-04-17 1:31 ` dpdklab
2025-04-17 1:43 ` dpdklab
2025-04-17 1:44 ` |PENDING| " dpdklab
2025-04-17 1:45 ` |SUCCESS| " dpdklab
2025-04-17 1:45 ` dpdklab
2025-04-17 1:51 ` dpdklab [this message]
2025-04-17 1:59 ` dpdklab
2025-04-17 2:01 ` dpdklab
2025-04-17 2:04 ` dpdklab
2025-04-17 2:17 ` dpdklab
2025-04-17 2:29 ` dpdklab
2025-04-17 2:31 ` dpdklab
2025-04-17 2:34 ` dpdklab
2025-04-17 2:34 ` dpdklab
2025-04-17 2:37 ` dpdklab
2025-04-17 2:43 ` dpdklab
2025-04-17 2:47 ` dpdklab
2025-04-17 2:53 ` dpdklab
2025-04-17 2:54 ` dpdklab
2025-04-17 3:07 ` dpdklab
2025-04-17 3:07 ` dpdklab
2025-04-17 3:17 ` dpdklab
2025-04-17 3:19 ` |PENDING| " dpdklab
2025-04-17 3:20 ` |SUCCESS| " dpdklab
2025-04-17 3:22 ` dpdklab
2025-04-17 3:27 ` dpdklab
2025-04-17 3:29 ` dpdklab
2025-04-17 3:39 ` dpdklab
2025-04-17 3:41 ` |PENDING| " dpdklab
2025-04-17 3:43 ` dpdklab
2025-04-17 3:50 ` dpdklab
2025-04-17 3:58 ` |SUCCESS| " dpdklab
2025-04-17 4:13 ` dpdklab
2025-04-17 4:13 ` dpdklab
2025-04-17 4:27 ` dpdklab
2025-04-17 4:28 ` dpdklab
2025-04-17 4:52 ` dpdklab
2025-04-17 6:14 ` dpdklab
2025-04-17 6:17 ` dpdklab
2025-04-17 6:22 ` dpdklab
2025-04-17 7:02 ` dpdklab
2025-04-17 7:07 ` dpdklab
2025-04-17 7:17 ` dpdklab
2025-04-17 7:42 ` dpdklab
2025-04-17 7:47 ` dpdklab
2025-04-17 8:54 ` dpdklab
2025-04-17 9:00 ` dpdklab
2025-04-17 17:53 ` dpdklab
2025-04-17 17:58 ` 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=68005e87.050a0220.31ab6d.8dedSMTPIN_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).