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| pw158765-158768 [PATCH] [v5,4/4] vhost_user: Function defs
Date: Thu, 13 Nov 2025 05:46:59 -0800 (PST) [thread overview]
Message-ID: <6915e153.170a0220.315a52.ae8dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251113124425.2913881-5-pravin.bathija@dell.com>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/158768
_Functional Testing PASS_
Submitter: Bathija, Pravin <pravin.bathija@dell.com>
Date: Thursday, November 13 2025 12:44:25
DPDK git baseline: Repo:dpdk-next-virtio
Branch: master
CommitID:6b37c26a95388aa41bb5267c7c42f604fd571a38
158765-158768 --> functional testing pass
Upstream job id: Template-DPDK-DTS-Pipeline#3252
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/34576/
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-11-13 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251113124425.2913881-5-pravin.bathija@dell.com>
2025-11-13 12:26 ` |SUCCESS| pw158765-158768 [PATCH v5 4/4] vhost_user: Function defs for add/rem mem regions qemudev
2025-11-13 12:31 ` qemudev
2025-11-13 12:45 ` |SUCCESS| pw158768 " checkpatch
2025-11-13 13:43 ` |PENDING| pw158765-158768 [PATCH] [v5,4/4] vhost_user: Function defs dpdklab
2025-11-13 13:46 ` dpdklab [this message]
2025-11-13 13:50 ` |SUCCESS| " dpdklab
2025-11-13 13:54 ` dpdklab
2025-11-13 14:04 ` dpdklab
2025-11-13 14:46 ` |PENDING| " dpdklab
2025-11-13 14:54 ` |SUCCESS| " dpdklab
2025-11-13 14:57 ` |SUCCESS| pw158768 [PATCH v5 4/4] vhost_user: Function defs for add/rem mem regions 0-day Robot
2025-11-13 14:57 ` 0-day Robot
2025-11-13 15:26 ` |SUCCESS| pw158765-158768 [PATCH] [v5,4/4] vhost_user: Function defs dpdklab
2025-11-13 15:47 ` dpdklab
2025-11-13 15:48 ` dpdklab
2025-11-13 16:03 ` 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=6915e153.170a0220.315a52.ae8dSMTPIN_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).