From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153180 [PATCH] [v2] net/iavf: support Rx/Tx burst mode i
Date: Mon, 28 Apr 2025 21:28:54 -0700 (PDT) [thread overview]
Message-ID: <68105586.050a0220.0db1.16b3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250428220712.571492-1-rmelton@cisco.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/153180
_Functional Testing PASS_
Submitter: Roger Melton <rmelton@cisco.com>
Date: Monday, April 28 2025 22:07:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ecadeeb16e75595c1420f7b77a66013893c399dd
153180 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#223428
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-131-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 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/33081/
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-29 4:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250428220712.571492-1-rmelton@cisco.com>
2025-04-28 21:37 ` |SUCCESS| pw153180 [PATCH v2] net/iavf: support Rx/Tx burst mode info qemudev
2025-04-28 21:41 ` qemudev
2025-04-28 22:12 ` checkpatch
2025-04-28 23:04 ` 0-day Robot
2025-04-29 4:01 ` |SUCCESS| pw153180 [PATCH] [v2] net/iavf: support Rx/Tx burst mode i dpdklab
2025-04-29 4:18 ` dpdklab
2025-04-29 4:26 ` dpdklab
2025-04-29 4:28 ` dpdklab [this message]
2025-04-29 4:30 ` dpdklab
2025-04-29 4:31 ` dpdklab
2025-04-29 4:57 ` dpdklab
2025-04-29 5:01 ` dpdklab
2025-04-29 5:06 ` |PENDING| " dpdklab
2025-04-29 5:09 ` dpdklab
2025-04-29 5:13 ` dpdklab
2025-04-29 5:54 ` |SUCCESS| " dpdklab
2025-04-29 5:58 ` dpdklab
2025-04-29 6:18 ` |PENDING| " dpdklab
2025-04-29 7:12 ` |SUCCESS| " dpdklab
2025-04-29 7:13 ` dpdklab
2025-04-29 7:23 ` dpdklab
2025-04-29 7:59 ` 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=68105586.050a0220.0db1.16b3SMTPIN_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).