From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw158223-158224 [PATCH] [3/3] net/mlx5: support flow metad
Date: Wed, 29 Oct 2025 09:42:03 -0700 (PDT) [thread overview]
Message-ID: <690243db.050a0220.9376c.5fb3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251029155711.169580-3-getelson@nvidia.com>
Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/158224
_Testing pending_
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 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#439083
Test environment and result as below:
+------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PEND |
+------------------------------+--------------------+
| Ubuntu 20.04 | PEND |
+------------------------------+--------------------+
| Debian GNU/Linux 12 | PEND |
+------------------------------+--------------------+
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04
Kernel: 5.15
Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
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:42 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 ` |SUCCESS| pw158223-158224 [PATCH] [3/3] net/mlx5: support flow metad dpdklab
2025-10-29 16:38 ` |PENDING| " dpdklab
2025-10-29 16:42 ` dpdklab [this message]
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=690243db.050a0220.9376c.5fb3SMTPIN_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).