From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw153528-153536 [PATCH] [9/9] crypto/dpaa2_sec: add suppor
Date: Tue, 20 May 2025 00:28:43 -0700 (PDT) [thread overview]
Message-ID: <682c2f2b.630a0220.238b0c.d621SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250520055133.506071-9-g.singh@nxp.com>
Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/153536
_Testing pending_
Submitter: Gagandeep Singh <g.singh@nxp.com>
Date: Tuesday, May 20 2025 05:51:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:117e86c4b96ed761e9a7ab766261208fe81bf5ca
153528-153536 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#389644
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| RHEL9 (ARM) | PEND |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PEND |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
| Debian 12 with MUSDK | PEND |
+------------------------------------+--------------------+
| Fedora 40 (ARM) | PEND |
+------------------------------------+--------------------+
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: Depends on container host
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33211/
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-05-20 7:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250520055133.506071-9-g.singh@nxp.com>
2025-05-20 5:27 ` |SUCCESS| pw153528-153536 [PATCH 9/9] crypto/dpaa2_sec: add support for simple IPsec FD qemudev
2025-05-20 5:32 ` qemudev
2025-05-20 5:55 ` |WARNING| pw153536 " checkpatch
2025-05-20 6:31 ` |SUCCESS| pw153528-153536 [PATCH] [9/9] crypto/dpaa2_sec: add suppor dpdklab
2025-05-20 6:38 ` dpdklab
2025-05-20 6:42 ` dpdklab
2025-05-20 6:44 ` dpdklab
2025-05-20 6:48 ` dpdklab
2025-05-20 6:55 ` dpdklab
2025-05-20 6:58 ` dpdklab
2025-05-20 7:01 ` |PENDING| " dpdklab
2025-05-20 7:02 ` |SUCCESS| " dpdklab
2025-05-20 7:02 ` |PENDING| " dpdklab
2025-05-20 7:09 ` |SUCCESS| " dpdklab
2025-05-20 7:14 ` dpdklab
2025-05-20 7:28 ` dpdklab [this message]
2025-05-20 7:55 ` dpdklab
2025-05-20 9:23 ` |PENDING| " dpdklab
2025-05-20 9:26 ` |FAILURE| " dpdklab
2025-05-20 9:56 ` dpdklab
2025-05-20 9:57 ` dpdklab
2025-05-20 10:02 ` |SUCCESS| " dpdklab
2025-05-20 10:47 ` |FAILURE| " dpdklab
2025-05-20 11:24 ` dpdklab
2025-05-20 11:32 ` dpdklab
2025-05-20 12:11 ` |SUCCESS| " dpdklab
2025-05-20 13:54 ` |FAILURE| " 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=682c2f2b.630a0220.238b0c.d621SMTPIN_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).