From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw156495-156500 [PATCH] [v2,7/7] net/ntnic: cleanup using
Date: Tue, 09 Sep 2025 23:00:37 -0700 (PDT) [thread overview]
Message-ID: <68c11405.0d0a0220.c532b.9058SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250908141740.1312268-8-sil-plv@napatech.com>
Test-Label: iol-unit-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/156500
_Testing pending_
Submitter: Serhii Iliushyk <sil-plv@napatech.com>
Date: Monday, September 08 2025 14:17:39
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:027d974ef56f7312133934422ea0f8971c224603
156495-156500 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#369738
Test environment and result as below:
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Environment | lpm_autotest | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+==============================+==============+==============================+===========================+================+
| Ubuntu 20.04 | PASS | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Debian 12 (arm) | SKIPPED | PEND | PEND | SKIPPED |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| CentOS Stream 10 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Debian GNU/Linux 12 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Fedora Linux 42 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| CentOS Stream 9 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Ubuntu 22.04 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Red Hat Enterprise Linux 9.5 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Fedora Linux 40 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Ubuntu 24.04 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
| Fedora Linux 41 | SKIPPED | SKIPPED | SKIPPED | PEND |
+------------------------------+--------------+------------------------------+---------------------------+----------------+
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
CentOS Stream 10
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 42
Kernel: 5.4
Compiler: clang gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)
CentOS Stream 9
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
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)
Fedora Linux 40
Kernel: 5.4
Compiler: clang 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
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34034/
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-10 6:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250908141740.1312268-8-sil-plv@napatech.com>
2025-09-08 13:46 ` |SUCCESS| pw156495-156500 [PATCH v2 7/7] net/ntnic: cleanup using pthreads and rte_thread qemudev
2025-09-08 13:51 ` qemudev
2025-09-08 14:17 ` |SUCCESS| pw156500 " checkpatch
2025-09-08 16:55 ` 0-day Robot
2025-09-08 16:55 ` 0-day Robot
2025-09-10 5:49 ` |PENDING| pw156495-156500 [PATCH] [v2,7/7] net/ntnic: cleanup using dpdklab
2025-09-10 5:56 ` |SUCCESS| " dpdklab
2025-09-10 5:59 ` |PENDING| " dpdklab
2025-09-10 6:00 ` |SUCCESS| " dpdklab
2025-09-10 6:00 ` dpdklab [this message]
2025-09-10 6:09 ` dpdklab
2025-09-10 6:11 ` dpdklab
2025-09-10 6:38 ` dpdklab
2025-09-10 6:41 ` |PENDING| " dpdklab
2025-09-10 6:42 ` |SUCCESS| " dpdklab
2025-09-10 7:11 ` dpdklab
2025-09-10 7:11 ` dpdklab
2025-09-10 7:46 ` |WARNING| " dpdklab
2025-09-10 9:12 ` |SUCCESS| " dpdklab
2025-09-10 9:54 ` dpdklab
2025-09-10 9:57 ` 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=68c11405.0d0a0220.c532b.9058SMTPIN_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).