From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| pw158098 [PATCH] compressdev: fix coverity issue
Date: Fri, 24 Oct 2025 14:26:10 -0700 (PDT) [thread overview]
Message-ID: <68fbeef2.170a0220.2c6c41.12b2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251024191108.1728811-1-svaze@qti.qualcomm.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/158098
_Testing PASS_
Submitter: Sameer Vaze <svaze@qti.qualcomm.com>
Date: Friday, October 24 2025 19:11:08
DPDK git baseline: Repo:dpdk-next-crypto
Branch: master
CommitID:6edcec237e31fcdb848cca6c151ee7a5bf057c28
158098 --> testing pass
Upstream job id: Windows-Compile-DPDK-Native#31886
Test environment and result as below:
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_llvm_clang_compile | dpdk_mingw64_compile |
+=====================+====================+===================+=========================+======================+
| Ubuntu 20.04 | PASS | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| FreeBSD 14.2 | PASS | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| Windows Server 2022 | SKIPPED | PASS | 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/34381/
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-24 21:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251024191108.1728811-1-svaze@qti.qualcomm.com>
2025-10-24 18:48 ` qemudev
2025-10-24 18:53 ` qemudev
2025-10-24 19:12 ` checkpatch
2025-10-24 20:04 ` |PENDING| " dpdklab
2025-10-24 20:05 ` |SUCCESS| " dpdklab
2025-10-24 20:07 ` dpdklab
2025-10-24 20:11 ` dpdklab
2025-10-24 20:17 ` |PENDING| " dpdklab
2025-10-24 20:19 ` |WARNING| " dpdklab
2025-10-24 20:43 ` |SUCCESS| " dpdklab
2025-10-24 20:53 ` |PENDING| " dpdklab
2025-10-24 21:03 ` |SUCCESS| " dpdklab
2025-10-24 21:07 ` dpdklab
2025-10-24 21:09 ` 0-day Robot
2025-10-24 21:09 ` 0-day Robot
2025-10-24 21:17 ` |PENDING| " dpdklab
2025-10-24 21:24 ` |SUCCESS| " dpdklab
2025-10-24 21:26 ` dpdklab [this message]
2025-10-24 21:43 ` dpdklab
2025-10-24 22:41 ` |WARNING| " dpdklab
2025-10-24 23:31 ` |SUCCESS| " dpdklab
2025-10-24 23:44 ` dpdklab
2025-10-24 23:53 ` dpdklab
2025-10-24 23:56 ` dpdklab
2025-10-25 1:04 ` 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=68fbeef2.170a0220.2c6c41.12b2SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gakhil@marvell.com \
--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).