From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw152787 [PATCH] [1/1] examples/ipsec-secgw: resolve segfa
Date: Mon, 07 Apr 2025 04:12:10 -0700 (PDT) [thread overview]
Message-ID: <67f3b30a.050a0220.24900e.66b1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250407072155.1255817-1-rkudurumalla@marvell.com>
Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/152787
_Testing pending_
Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Monday, April 07 2025 07:21:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0c4fb260a3dd4e977e88cbf5c8e39289bcc94520
152787 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#377965
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| RHEL9 (ARM) | PEND |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PEND |
+------------------------------------+--------------------+
| Fedora 40 (ARM) | PEND |
+------------------------------------+--------------------+
| Debian 12 with MUSDK | PEND |
+------------------------------------+--------------------+
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
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
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Debian 12 with MUSDK
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/32951/
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-04-07 11:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250407072155.1255817-1-rkudurumalla@marvell.com>
2025-04-07 6:56 ` |SUCCESS| pw152787 [PATCH 1/1] examples/ipsec-secgw: resolve segfault for IPsec packets qemudev
2025-04-07 7:00 ` qemudev
2025-04-07 7:22 ` checkpatch
2025-04-07 8:22 ` 0-day Robot
2025-04-07 9:23 ` |SUCCESS| pw152787 [PATCH] [1/1] examples/ipsec-secgw: resolve segfa dpdklab
2025-04-07 9:36 ` dpdklab
2025-04-07 9:36 ` dpdklab
2025-04-07 9:36 ` dpdklab
2025-04-07 9:37 ` dpdklab
2025-04-07 9:44 ` dpdklab
2025-04-07 9:48 ` dpdklab
2025-04-07 9:48 ` |PENDING| " dpdklab
2025-04-07 9:50 ` |SUCCESS| " dpdklab
2025-04-07 9:56 ` dpdklab
2025-04-07 10:00 ` dpdklab
2025-04-07 10:03 ` dpdklab
2025-04-07 10:11 ` dpdklab
2025-04-07 10:33 ` |PENDING| " dpdklab
2025-04-07 10:49 ` |SUCCESS| " dpdklab
2025-04-07 10:52 ` |PENDING| " dpdklab
2025-04-07 11:04 ` |SUCCESS| " dpdklab
2025-04-07 11:04 ` dpdklab
2025-04-07 11:12 ` dpdklab [this message]
2025-04-07 11:49 ` dpdklab
2025-04-07 11:54 ` dpdklab
2025-04-07 12:44 ` dpdklab
2025-04-07 12:57 ` dpdklab
2025-04-07 19:39 ` 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=67f3b30a.050a0220.24900e.66b1SMTPIN_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).