automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154564 [PATCH] [v2,1/1] examples/ipsec-secgw: resolve se
Date: Wed, 18 Jun 2025 09:01:49 -0700 (PDT)	[thread overview]
Message-ID: <6852e2ed.170a0220.33061.4c6bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250618083006.1679656-1-rkudurumalla@marvell.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/154564

_Testing PASS_

Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Wednesday, June 18 2025 08:30:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d

154564 --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#29150

Test environment and result as below:

+---------------------+--------------------+-------------------+-------------------------+
|     Environment     | dpdk_meson_compile | dpdk_msvc_compile | dpdk_llvm_clang_compile |
+=====================+====================+===================+=========================+
| Ubuntu 20.04        | PASS               | SKIPPED           | SKIPPED                 |
+---------------------+--------------------+-------------------+-------------------------+
| FreeBSD 14.2        | PASS               | SKIPPED           | SKIPPED                 |
+---------------------+--------------------+-------------------+-------------------------+
| Windows Server 2022 | SKIPPED            | PASS              | PASS                    |
+---------------------+--------------------+-------------------+-------------------------+


Ubuntu 20.04
	Kernel: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33450/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-06-18 16:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250618083006.1679656-1-rkudurumalla@marvell.com>
2025-06-18  7:57 ` |SUCCESS| pw154564 [PATCH v2 1/1] examples/ipsec-secgw: resolve segfault for IPsec packets qemudev
2025-06-18  8:01 ` qemudev
2025-06-18  8:29 ` checkpatch
2025-06-18  9:45 ` 0-day Robot
2025-06-18 14:08 ` |SUCCESS| pw154564 [PATCH] [v2,1/1] examples/ipsec-secgw: resolve se dpdklab
2025-06-18 14:18 ` |PENDING| " dpdklab
2025-06-18 14:19 ` |SUCCESS| " dpdklab
2025-06-18 14:25 ` dpdklab
2025-06-18 14:44 ` dpdklab
2025-06-18 14:54 ` dpdklab
2025-06-18 15:09 ` dpdklab
2025-06-18 15:12 ` |PENDING| " dpdklab
2025-06-18 15:22 ` |SUCCESS| " dpdklab
2025-06-18 15:27 ` dpdklab
2025-06-18 15:35 ` |PENDING| " dpdklab
2025-06-18 16:01 ` dpdklab [this message]
2025-06-18 16:11 ` |SUCCESS| " dpdklab
2025-06-18 18:20 ` |PENDING| " dpdklab
2025-06-18 19:30 ` |WARNING| " dpdklab
2025-06-18 19:32 ` dpdklab
2025-06-18 19:32 ` dpdklab
2025-06-18 19:33 ` dpdklab
2025-06-18 19:33 ` 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=6852e2ed.170a0220.33061.4c6bSMTPIN_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).