From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw146197 [PATCH] crypto/openssl: fix potential string over
Date: Thu, 17 Oct 2024 11:14:13 -0700 (PDT) [thread overview]
Message-ID: <671153f5.050a0220.b7905.2b05SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241017160754.132762-1-stephen@networkplumber.org>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/146197
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, October 17 2024 16:07:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:98613d32e3dac58d685f4f236cf8cc9733abaaf3
146197 --> testing pass
Upstream job id: Generic-VM-DPDK-Compile-Meson#30388
Test environment and result as below:
+---------------------+-------------------+--------------------+
| Environment | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+===================+====================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+-------------------+--------------------+
| FreeBSD 13.4 | SKIPPED | PASS |
+---------------------+-------------------+--------------------+
| FreeBSD 14.1 | SKIPPED | PASS |
+---------------------+-------------------+--------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
FreeBSD 13.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31538/
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-10-17 18:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241017160754.132762-1-stephen@networkplumber.org>
2024-10-17 15:41 ` |SUCCESS| pw146197 [PATCH] crypto/openssl: fix potential string overflow qemudev
2024-10-17 15:45 ` qemudev
2024-10-17 16:09 ` checkpatch
2024-10-17 17:05 ` 0-day Robot
2024-10-17 17:52 ` |SUCCESS| pw146197 [PATCH] crypto/openssl: fix potential string over dpdklab
2024-10-17 17:55 ` dpdklab
2024-10-17 17:57 ` dpdklab
2024-10-17 17:57 ` |PENDING| " dpdklab
2024-10-17 18:02 ` |SUCCESS| " dpdklab
2024-10-17 18:03 ` dpdklab
2024-10-17 18:05 ` dpdklab
2024-10-17 18:07 ` dpdklab
2024-10-17 18:11 ` dpdklab
2024-10-17 18:11 ` |PENDING| " dpdklab
2024-10-17 18:14 ` dpdklab [this message]
2024-10-17 18:25 ` |SUCCESS| " dpdklab
2024-10-17 18:25 ` |PENDING| " dpdklab
2024-10-17 18:31 ` |FAILURE| " dpdklab
2024-10-17 18:31 ` |SUCCESS| " dpdklab
2024-10-17 18:35 ` dpdklab
2024-10-17 19:16 ` |FAILURE| " dpdklab
2024-10-17 20:43 ` |PENDING| " dpdklab
2024-10-17 21:19 ` |SUCCESS| " dpdklab
2024-10-17 22:30 ` dpdklab
2024-10-18 1:00 ` |WARNING| " dpdklab
2024-10-18 1:57 ` |SUCCESS| " dpdklab
2024-10-20 3:45 ` dpdklab
2024-10-23 5:02 ` 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=671153f5.050a0220.b7905.2b05SMTPIN_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).