From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw158208 [PATCH] [v2] config/arm: add HiSilicon HIP12
Date: Tue, 28 Oct 2025 19:12:48 -0700 (PDT) [thread overview]
Message-ID: <69017820.050a0220.2d3ff5.1f5dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251029011626.9298-1-fengchengwen@huawei.com>
Test-Label: iol-unit-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/158208
_Testing pending_
Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Wednesday, October 29 2025 01:16:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39b54f2dcf44ad1f91eabc7080cd5dea763607fd
158208 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#386474
Test environment and result as below:
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest | lpm_autotest | cryptodev_sw_zuc_autotest |
+==============================+================+==============================+==============+===========================+
| CentOS Stream 10 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| CentOS Stream 9 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora Linux 40 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora Linux 42 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Debian GNU/Linux 12 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora Linux 41 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 20.04 | PEND | SKIPPED | PASS | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 22.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Red Hat Enterprise Linux 9.5 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 24.04 | PEND | SKIPPED | SKIPPED | SKIPPED |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
| Debian 12 (arm) | SKIPPED | PEND | SKIPPED | PEND |
+------------------------------+----------------+------------------------------+--------------+---------------------------+
CentOS Stream 10
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)
CentOS Stream 9
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-11)
Fedora Linux 40
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 42
Kernel: 5.4
Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 41
Kernel: 5.4
Compiler: clang gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
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)
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/34411/
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 2:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251029011626.9298-1-fengchengwen@huawei.com>
2025-10-29 0:41 ` |SUCCESS| pw158208 [PATCH v2] " qemudev
2025-10-29 0:46 ` qemudev
2025-10-29 1:17 ` checkpatch
2025-10-29 1:41 ` |PENDING| pw158208 [PATCH] [v2] " dpdklab
2025-10-29 1:44 ` |SUCCESS| " dpdklab
2025-10-29 1:52 ` |PENDING| " dpdklab
2025-10-29 1:53 ` dpdklab
2025-10-29 1:54 ` |FAILURE| " dpdklab
2025-10-29 2:00 ` |SUCCESS| " dpdklab
2025-10-29 2:04 ` dpdklab
2025-10-29 2:05 ` |WARNING| " dpdklab
2025-10-29 2:06 ` |SUCCESS| " dpdklab
2025-10-29 2:12 ` dpdklab [this message]
2025-10-29 2:14 ` |SUCCESS| pw158208 [PATCH v2] " 0-day Robot
2025-10-29 2:14 ` 0-day Robot
2025-10-29 2:18 ` |SUCCESS| pw158208 [PATCH] [v2] " dpdklab
2025-10-29 2:21 ` dpdklab
2025-10-29 2:25 ` |WARNING| " dpdklab
2025-10-29 2:28 ` dpdklab
2025-10-29 2:28 ` |SUCCESS| " dpdklab
2025-10-29 3:59 ` dpdklab
2025-10-29 4:52 ` dpdklab
2025-10-29 4:55 ` dpdklab
2025-10-29 5:05 ` dpdklab
2025-10-29 6:12 ` dpdklab
2025-10-29 18:59 ` 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=69017820.050a0220.2d3ff5.1f5dSMTPIN_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).