From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw158223-158224 [PATCH] [3/3] net/mlx5: support flow metad
Date: Wed, 29 Oct 2025 09:29:33 -0700 (PDT) [thread overview]
Message-ID: <690240ed.050a0220.30cbc9.76b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251029155711.169580-3-getelson@nvidia.com>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/158224
_Functional Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wednesday, October 29 2025 15:57:10
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:39b54f2dcf44ad1f91eabc7080cd5dea763607fd
158223-158224 --> functional testing pass
Upstream job id: Template-DPDK-DTS-Pipeline#2796
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/34418/
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-29 16:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251029155711.169580-3-getelson@nvidia.com>
2025-10-29 15:25 ` |SUCCESS| pw158223-158224 [PATCH 3/3] net/mlx5: support flow metadata exchange between E-Switch and VM qemudev
2025-10-29 15:30 ` qemudev
2025-10-29 16:00 ` |SUCCESS| pw158224 " checkpatch
2025-10-29 16:29 ` dpdklab [this message]
2025-10-29 16:38 ` |PENDING| pw158223-158224 [PATCH] [3/3] net/mlx5: support flow metad dpdklab
2025-10-29 16:42 ` dpdklab
2025-10-29 16:43 ` |SUCCESS| " dpdklab
2025-10-29 16:47 ` |PENDING| " dpdklab
2025-10-29 16:58 ` dpdklab
2025-10-29 16:59 ` |WARNING| " dpdklab
2025-10-29 17:03 ` |SUCCESS| " dpdklab
2025-10-29 17:06 ` |PENDING| " dpdklab
2025-10-29 17:09 ` |SUCCESS| " dpdklab
2025-10-29 17:10 ` |WARNING| " dpdklab
2025-10-29 17:38 ` |SUCCESS| " dpdklab
2025-10-29 17:41 ` dpdklab
2025-10-29 17:54 ` |WARNING| " dpdklab
2025-10-29 18:08 ` |SUCCESS| " dpdklab
2025-10-29 18:09 ` |FAILURE| pw158224 [PATCH 3/3] net/mlx5: support flow metadata exchange between E-Switch and VM 0-day Robot
2025-10-29 18:12 ` |WARNING| pw158223-158224 [PATCH] [3/3] net/mlx5: support flow metad dpdklab
2025-10-29 18:15 ` |SUCCESS| " dpdklab
2025-10-29 18:24 ` dpdklab
2025-10-29 18:35 ` dpdklab
2025-10-29 18:38 ` dpdklab
2025-10-29 19:04 ` |WARNING| " dpdklab
2025-10-29 19:48 ` dpdklab
2025-10-30 3:42 ` |SUCCESS| " 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=690240ed.050a0220.30cbc9.76b6SMTPIN_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).