From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143195 [PATCH] [v1] examples/ipsec-secgw: free the actua
Date: Fri, 16 Aug 2024 02:55:12 -0700 (PDT) [thread overview]
Message-ID: <66bf2200.6b0a0220.374abf.6163SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240816072236.3686666-1-vvelumuri@marvell.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143195
_Testing PASS_
Submitter: Vidya Sagar Velumuri <vvelumuri@marvell.com>
Date: Friday, August 16 2024 07:22:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143195 --> testing pass
Upstream job id: Windows-Compile-DPDK-Native#21555
Test environment and result as below:
+---------------------+-----------------------+----------------------+--------------------+
| Environment | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_meson_compile |
+=====================+=======================+======================+====================+
| Windows Server 2022 | PASS | PASS | SKIPPED |
+---------------------+-----------------------+----------------------+--------------------+
| FreeBSD 14.1 | SKIPPED | SKIPPED | PASS |
+---------------------+-----------------------+----------------------+--------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30800/
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:[~2024-08-16 9:55 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240816072236.3686666-1-vvelumuri@marvell.com>
2024-08-16 6:55 ` |SUCCESS| pw143195 [PATCH v1] examples/ipsec-secgw: free the actual mbuf pointer qemudev
2024-08-16 6:59 ` qemudev
2024-08-16 7:24 ` checkpatch
2024-08-16 8:22 ` 0-day Robot
2024-08-16 9:05 ` |SUCCESS| pw143195 [PATCH] [v1] examples/ipsec-secgw: free the actua dpdklab
2024-08-16 9:05 ` dpdklab
2024-08-16 9:08 ` dpdklab
2024-08-16 9:09 ` dpdklab
2024-08-16 9:09 ` dpdklab
2024-08-16 9:09 ` dpdklab
2024-08-16 9:11 ` dpdklab
2024-08-16 9:12 ` |PENDING| " dpdklab
2024-08-16 9:13 ` |SUCCESS| " dpdklab
2024-08-16 9:13 ` dpdklab
2024-08-16 9:22 ` dpdklab
2024-08-16 9:27 ` dpdklab
2024-08-16 9:28 ` dpdklab
2024-08-16 9:29 ` dpdklab
2024-08-16 9:30 ` dpdklab
2024-08-16 9:33 ` |PENDING| " dpdklab
2024-08-16 9:35 ` |SUCCESS| " dpdklab
2024-08-16 9:40 ` dpdklab
2024-08-16 9:40 ` dpdklab
2024-08-16 9:48 ` dpdklab
2024-08-16 9:54 ` dpdklab
2024-08-16 9:55 ` dpdklab [this message]
2024-08-16 9:57 ` dpdklab
2024-08-16 9:57 ` dpdklab
2024-08-16 10:01 ` dpdklab
2024-08-16 10:04 ` |PENDING| " dpdklab
2024-08-16 10:05 ` |SUCCESS| " dpdklab
2024-08-16 10:06 ` dpdklab
2024-08-16 10:14 ` dpdklab
2024-08-16 10:29 ` dpdklab
2024-08-16 10:37 ` dpdklab
2024-08-16 10:37 ` dpdklab
2024-08-16 10:42 ` dpdklab
2024-08-16 10:42 ` dpdklab
2024-08-16 11:24 ` dpdklab
2024-08-16 11:24 ` dpdklab
2024-08-16 11:24 ` dpdklab
2024-08-16 11:24 ` dpdklab
2024-08-16 11:24 ` dpdklab
2024-08-16 11:25 ` dpdklab
2024-08-16 11:25 ` dpdklab
2024-08-16 11:25 ` dpdklab
2024-08-16 11:26 ` dpdklab
2024-08-16 11:26 ` dpdklab
2024-08-16 11:27 ` dpdklab
2024-08-16 11:27 ` dpdklab
2024-08-16 11:27 ` dpdklab
2024-08-16 11:27 ` dpdklab
2024-08-16 11:27 ` dpdklab
2024-08-16 11:28 ` dpdklab
2024-08-16 11:29 ` dpdklab
2024-08-16 11:31 ` dpdklab
2024-08-16 11:31 ` dpdklab
2024-08-16 11:32 ` dpdklab
2024-08-16 11:32 ` dpdklab
2024-08-16 11:33 ` dpdklab
2024-08-16 11:34 ` dpdklab
2024-08-16 11:35 ` dpdklab
2024-08-16 11:46 ` dpdklab
2024-08-16 11:48 ` dpdklab
2024-08-16 12:03 ` dpdklab
2024-08-16 12:14 ` dpdklab
2024-08-16 12:49 ` dpdklab
2024-08-16 15:53 ` 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=66bf2200.6b0a0220.374abf.6163SMTPIN_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).