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| pw159577-159580 [PATCH] [v2,5/5] net/zxdh: add support GEN
Date: Thu, 08 Jan 2026 14:41:53 -0800 (PST) [thread overview]
Message-ID: <696032b1.050a0220.2336e2.fb5eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260105071643.1119116-6-wang.junlong1@zte.com.cn>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/159580
_Functional Testing PASS_
Submitter: Junlong Wang <wang.junlong1@zte.com.cn>
Date: Monday, January 05 2026 07:16:43
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:986a1b63892f24df8928216daeec53f034f1e0a4
159577-159580 --> functional testing pass
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 |
+---------------------------------+--------+
| hello_world | PASS |
+---------------------------------+--------+
| l2fwd | PASS |
+---------------------------------+--------+
| port_restart_config_persistency | PASS |
+---------------------------------+--------+
| packet_capture | PASS |
+---------------------------------+--------+
| softnic | PASS |
+---------------------------------+--------+
| vlan | PASS |
+---------------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34813/
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:[~2026-01-08 22:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260105071643.1119116-6-wang.junlong1@zte.com.cn>
2026-01-05 7:39 ` |SUCCESS| pw159580 [PATCH v2 5/5] net/zxdh: add support GENEVE TSO and Rx outer chksum checkpatch
2026-01-05 8:01 ` |SUCCESS| pw159577-159580 " qemudev
2026-01-05 8:06 ` qemudev
2026-01-05 8:24 ` |SUCCESS| pw159580 " 0-day Robot
2026-01-05 8:24 ` 0-day Robot
2026-01-08 0:01 ` |SUCCESS| pw159577-159580 [PATCH] [v2,5/5] net/zxdh: add support GEN dpdklab
2026-01-08 2:40 ` dpdklab
2026-01-08 6:54 ` dpdklab
2026-01-08 10:41 ` |PENDING| " dpdklab
2026-01-08 11:07 ` |SUCCESS| " dpdklab
2026-01-08 11:07 ` dpdklab
2026-01-08 11:16 ` dpdklab
2026-01-08 11:19 ` dpdklab
2026-01-08 21:35 ` dpdklab
2026-01-08 21:38 ` dpdklab
2026-01-08 22:06 ` dpdklab
2026-01-08 22:17 ` dpdklab
2026-01-08 22:23 ` dpdklab
2026-01-08 22:27 ` dpdklab
2026-01-08 22:36 ` dpdklab
2026-01-08 22:41 ` dpdklab [this message]
2026-01-09 22:53 ` dpdklab
2026-01-09 23:13 ` dpdklab
2026-01-10 2:45 ` |PENDING| " dpdklab
2026-01-10 4:34 ` |SUCCESS| " dpdklab
2026-01-10 4:42 ` 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=696032b1.050a0220.2336e2.fb5eSMTPIN_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).