From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw158089-158090 [PATCH] [v3,2/2] dts: add QinQ test suite
Date: Fri, 24 Oct 2025 11:47:03 -0700 (PDT) [thread overview]
Message-ID: <68fbc9a7.050a0220.3183fb.da41SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251024181606.604135-2-dmarx@iol.unh.edu>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/158090
_Functional Testing PASS_
Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Friday, October 24 2025 18:16:06
DPDK git baseline: Repo:dpdk-next-dts
Branch: master
CommitID:c1abcee5a9656fb4890b733e6051aa604c60f146
158089-158090 --> functional testing pass
Upstream job id: Template-DPDK-DTS-Pipeline#2667
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/34375/
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-24 18:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251024181606.604135-2-dmarx@iol.unh.edu>
2025-10-24 17:41 ` |SUCCESS| pw158089-158090 [PATCH v3 2/2] " qemudev
2025-10-24 17:46 ` qemudev
2025-10-24 18:16 ` |SUCCESS| pw158090 " checkpatch
2025-10-24 18:40 ` |FAILURE| pw158089-158090 [PATCH] [v3,2/2] " dpdklab
2025-10-24 18:43 ` |PENDING| " dpdklab
2025-10-24 18:47 ` dpdklab [this message]
2025-10-24 18:55 ` dpdklab
2025-10-24 18:56 ` |WARNING| " dpdklab
2025-10-24 19:03 ` |SUCCESS| " dpdklab
2025-10-24 19:05 ` dpdklab
2025-10-24 19:08 ` dpdklab
2025-10-24 19:08 ` |PENDING| " dpdklab
2025-10-24 19:11 ` |FAILURE| pw158090 [PATCH v3 2/2] " 0-day Robot
2025-10-24 19:12 ` |PENDING| pw158089-158090 [PATCH] [v3,2/2] " dpdklab
2025-10-24 19:15 ` |SUCCESS| " dpdklab
2025-10-24 19:38 ` |WARNING| " dpdklab
2025-10-24 20:07 ` |SUCCESS| " dpdklab
2025-10-24 20:08 ` dpdklab
2025-10-24 21:12 ` dpdklab
2025-10-24 22:40 ` dpdklab
2025-10-24 22:53 ` dpdklab
2025-10-24 23:22 ` dpdklab
2025-10-25 11:00 ` dpdklab
2025-10-25 15:09 ` |WARNING| " dpdklab
2025-10-25 16:02 ` dpdklab
2025-10-25 16:29 ` 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=68fbc9a7.050a0220.3183fb.da41SMTPIN_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).