From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw158990 [PATCH] net/mlx5: fix metadata sharing between E-
Date: Sun, 23 Nov 2025 10:17:56 -0800 (PST) [thread overview]
Message-ID: <69234fd4.170a0220.350364.4a80SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251123101242.1090544-1-getelson@nvidia.com>
Test-Label: iol-unit-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/158990
_Testing pending_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sunday, November 23 2025 10:12:42
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:9cf35632839ee84aad5a4baade86ea1dc8ba3d1b
158990 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#395325
Test environment and result as below:
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | lpm_autotest |
+==============================+================+==============================+===========================+==============+
| Fedora Linux 42 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Ubuntu 22.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Red Hat Enterprise Linux 9.5 | PASS | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| CentOS Stream 10 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Ubuntu 20.04 | PEND | SKIPPED | SKIPPED | PEND |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Fedora Linux 41 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| CentOS Stream 9 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Debian GNU/Linux 12 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Fedora Linux 40 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Ubuntu 24.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
| Debian 12 (arm) | SKIPPED | PEND | PEND | SKIPPED |
+------------------------------+----------------+------------------------------+---------------------------+--------------+
Fedora Linux 42
Kernel: 5.4
Compiler: clang gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)
Ubuntu 22.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
CentOS Stream 10
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
CentOS Stream 9
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 40
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Ubuntu 24.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34659/
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-11-23 18:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251123101242.1090544-1-getelson@nvidia.com>
2025-11-23 9:45 ` |SUCCESS| pw158990 [PATCH] net/mlx5: fix metadata sharing between E-Switch and VM qemudev
2025-11-23 9:50 ` qemudev
2025-11-23 10:12 ` checkpatch
2025-11-23 18:10 ` |PENDING| pw158990 [PATCH] net/mlx5: fix metadata sharing between E- dpdklab
2025-11-23 18:12 ` dpdklab
2025-11-23 18:12 ` |SUCCESS| " dpdklab
2025-11-23 18:16 ` |FAILURE| " dpdklab
2025-11-23 18:17 ` dpdklab [this message]
2025-11-23 18:21 ` |PENDING| " dpdklab
2025-11-23 18:31 ` |SUCCESS| " dpdklab
2025-11-23 18:33 ` dpdklab
2025-11-23 18:34 ` dpdklab
2025-11-23 18:34 ` dpdklab
2025-11-23 18:35 ` dpdklab
2025-11-23 18:47 ` dpdklab
2025-11-23 18:47 ` dpdklab
2025-11-23 18:53 ` dpdklab
2025-11-23 18:53 ` dpdklab
2025-11-23 18:53 ` dpdklab
2025-11-24 17:16 ` |FAILURE| " dpdklab
2025-11-24 17:50 ` dpdklab
2025-11-24 18:08 ` |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=69234fd4.170a0220.350364.4a80SMTPIN_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).