From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| pw157450 [PATCH] [v3] vhost: fix a double fetch when deque
Date: Fri, 10 Oct 2025 02:17:51 -0700 (PDT) [thread overview]
Message-ID: <68e8cf3f.050a0220.33940d.8482SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1760085696-35028-1-git-send-email-wangyunjian@huawei.com>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/157450
_Functional Testing PASS_
Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Friday, October 10 2025 08:41:36
DPDK git baseline: Repo:dpdk-next-virtio
Branch: master
CommitID:4159ea62922ce41566c7bab44655ad78bee85458
157450 --> functional testing pass
Upstream job id: Template-DPDK-DTS-Pipeline#2381
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 |
+=================================+========+
| blocklist | PASS |
+---------------------------------+--------+
| promisc_support | PASS |
+---------------------------------+--------+
| uni_pkt | PASS |
+---------------------------------+--------+
| dynamic_config | PASS |
+---------------------------------+--------+
| hello_world | PASS |
+---------------------------------+--------+
| l2fwd | PASS |
+---------------------------------+--------+
| port_restart_config_persistency | PASS |
+---------------------------------+--------+
| softnic | PASS |
+---------------------------------+--------+
| vlan | PASS |
+---------------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34250/
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-10-10 9:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1760085696-35028-1-git-send-email-wangyunjian@huawei.com>
2025-10-10 8:07 ` |SUCCESS| pw157450 [PATCH v3] vhost: fix a double fetch when dequeue offloading qemudev
2025-10-10 8:12 ` qemudev
2025-10-10 8:42 ` checkpatch
2025-10-10 9:15 ` |PENDING| pw157450 [PATCH] [v3] vhost: fix a double fetch when deque dpdklab
2025-10-10 9:16 ` |SUCCESS| " dpdklab
2025-10-10 9:17 ` dpdklab [this message]
2025-10-10 9:26 ` dpdklab
2025-10-10 9:34 ` |PENDING| " dpdklab
2025-10-10 9:37 ` |SUCCESS| " dpdklab
2025-10-10 9:39 ` dpdklab
2025-10-10 9:52 ` |PENDING| " dpdklab
2025-10-10 10:01 ` dpdklab
2025-10-10 10:26 ` |SUCCESS| " dpdklab
2025-10-10 10:28 ` dpdklab
2025-10-10 10:33 ` dpdklab
2025-10-10 10:38 ` |SUCCESS| pw157450 [PATCH v3] vhost: fix a double fetch when dequeue offloading 0-day Robot
2025-10-10 10:38 ` 0-day Robot
2025-10-10 11:08 ` |SUCCESS| pw157450 [PATCH] [v3] vhost: fix a double fetch when deque dpdklab
2025-10-10 11:09 ` dpdklab
2025-10-10 11:23 ` dpdklab
2025-10-10 11:51 ` dpdklab
2025-10-10 12:11 ` dpdklab
2025-10-10 12:14 ` dpdklab
2025-10-10 14:53 ` 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=68e8cf3f.050a0220.33940d.8482SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.com \
--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).