From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw157006-157007 [PATCH] [2/2] net/netvsc: rename get_vmbus
Date: Fri, 26 Sep 2025 09:27:27 -0700 (PDT) [thread overview]
Message-ID: <68d6beef.050a0220.588e8.4463SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250926155802.398869-2-stephen@networkplumber.org>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/157007
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, September 26 2025 15:58:01
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:0b58c147385ecd20ebb4e678934536a597902c28
157006-157007 --> functional testing pass
Upstream job id: Template-DPDK-DTS-Pipeline#2214
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/34160/
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-09-26 16:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250926155802.398869-2-stephen@networkplumber.org>
2025-09-26 15:35 ` |SUCCESS| pw157006-157007 [PATCH 2/2] net/netvsc: rename get_vmbus_device internal function qemudev
2025-09-26 15:40 ` qemudev
2025-09-26 15:56 ` |SUCCESS| pw157007 " checkpatch
2025-09-26 16:24 ` |PENDING| pw157006-157007 [PATCH] [2/2] net/netvsc: rename get_vmbus dpdklab
2025-09-26 16:27 ` dpdklab [this message]
2025-09-26 16:27 ` |SUCCESS| " dpdklab
2025-09-26 16:36 ` |PENDING| " dpdklab
2025-09-26 17:04 ` |SUCCESS| " dpdklab
2025-09-26 17:21 ` |PENDING| " dpdklab
2025-09-26 17:33 ` dpdklab
2025-09-26 18:14 ` |SUCCESS| " dpdklab
2025-09-26 18:25 ` dpdklab
2025-09-26 18:26 ` dpdklab
2025-09-26 18:29 ` dpdklab
2025-09-26 18:30 ` dpdklab
2025-09-26 19:22 ` dpdklab
2025-09-26 19:44 ` dpdklab
2025-09-26 20:11 ` dpdklab
2025-09-26 20:12 ` dpdklab
2025-09-26 20:20 ` dpdklab
2025-09-26 22:45 ` |FAILURE| pw157007 [PATCH 2/2] net/netvsc: rename get_vmbus_device internal function 0-day Robot
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=68d6beef.050a0220.588e8.4463SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).