From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw157047-157055 [PATCH] [v6,9/9] power: separate public an
Date: Tue, 30 Sep 2025 00:23:18 -0700 (PDT) [thread overview]
Message-ID: <68db8566.170a0220.2bd7f9.3eacSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250930065740.1838899-10-david.marchand@redhat.com>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/157055
_Functional Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, September 30 2025 06:57:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1d627ea13aeec2bcccf27246e6be2508370d171e
157047-157055 --> functional testing pass
Upstream job id: Template-DPDK-DTS-Pipeline#2242
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/34175/
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-30 7:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250930065740.1838899-10-david.marchand@redhat.com>
2025-09-30 6:44 ` |SUCCESS| pw157047-157055 [PATCH v6 9/9] power: separate public and driver headers qemudev
2025-09-30 6:49 ` qemudev
2025-09-30 6:59 ` |SUCCESS| pw157055 " checkpatch
2025-09-30 7:20 ` |PENDING| pw157047-157055 [PATCH] [v6,9/9] power: separate public an dpdklab
2025-09-30 7:23 ` dpdklab [this message]
2025-09-30 7:23 ` dpdklab
2025-09-30 7:26 ` |SUCCESS| " dpdklab
2025-09-30 7:31 ` |PENDING| " dpdklab
2025-09-30 7:40 ` |SUCCESS| " dpdklab
2025-09-30 7:42 ` dpdklab
2025-09-30 7:51 ` dpdklab
2025-09-30 7:57 ` |PENDING| " dpdklab
2025-09-30 7:57 ` |SUCCESS| " dpdklab
2025-09-30 8:02 ` dpdklab
2025-09-30 8:04 ` dpdklab
2025-09-30 8:09 ` dpdklab
2025-09-30 8:12 ` dpdklab
2025-09-30 8:12 ` dpdklab
2025-09-30 8:45 ` dpdklab
2025-09-30 8:46 ` |SUCCESS| pw157055 [PATCH v6 9/9] power: separate public and driver headers 0-day Robot
2025-09-30 8:46 ` 0-day Robot
2025-09-30 10:41 ` |SUCCESS| pw157047-157055 [PATCH] [v6,9/9] power: separate public an dpdklab
2025-09-30 10:41 ` dpdklab
2025-09-30 10:44 ` dpdklab
2025-09-30 11:05 ` |PENDING| " dpdklab
2025-09-30 11:10 ` |SUCCESS| " dpdklab
2025-09-30 11:20 ` dpdklab
2025-09-30 12:42 ` dpdklab
2025-09-30 13:37 ` dpdklab
2025-09-30 18:44 ` dpdklab
2025-10-01 0:14 ` dpdklab
2025-10-01 8:02 ` 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=68db8566.170a0220.2bd7f9.3eacSMTPIN_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).