From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140802-140806 [PATCH] [v3,5/5] crypto/openssl: only set
Date: Thu, 06 Jun 2024 08:26:19 -0700 (PDT) [thread overview]
Message-ID: <6661d51b.050a0220.34fbe8.56ebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240606102043.2926695-6-jack.bond-preston@foss.arm.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140806
_Testing PASS_
Submitter: Jack Bond-Preston <jack.bond-preston@foss.arm.com>
Date: Thursday, June 06 2024 10:20:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:367b8db312517edb9f5340d280e77b1437d84dd3
140802-140806 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30126/
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-06-06 15:26 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240606102043.2926695-6-jack.bond-preston@foss.arm.com>
2024-06-06 9:55 ` |SUCCESS| pw140802-140806 [PATCH v3 5/5] crypto/openssl: only set cipher padding once qemudev
2024-06-06 10:00 ` qemudev
2024-06-06 10:22 ` |SUCCESS| pw140806 " checkpatch
2024-06-06 11:24 ` 0-day Robot
2024-06-06 14:05 ` |SUCCESS| pw140802-140806 [PATCH] [v3,5/5] crypto/openssl: only set dpdklab
2024-06-06 14:07 ` dpdklab
2024-06-06 14:08 ` dpdklab
2024-06-06 14:08 ` dpdklab
2024-06-06 14:09 ` dpdklab
2024-06-06 14:10 ` dpdklab
2024-06-06 14:10 ` dpdklab
2024-06-06 14:11 ` dpdklab
2024-06-06 14:11 ` dpdklab
2024-06-06 14:12 ` dpdklab
2024-06-06 14:13 ` dpdklab
2024-06-06 14:13 ` dpdklab
2024-06-06 14:29 ` dpdklab
2024-06-06 14:29 ` dpdklab
2024-06-06 14:30 ` dpdklab
2024-06-06 14:30 ` dpdklab
2024-06-06 14:31 ` dpdklab
2024-06-06 14:32 ` dpdklab
2024-06-06 14:34 ` dpdklab
2024-06-06 14:36 ` dpdklab
2024-06-06 14:36 ` dpdklab
2024-06-06 14:37 ` dpdklab
2024-06-06 14:37 ` dpdklab
2024-06-06 14:38 ` dpdklab
2024-06-06 14:39 ` dpdklab
2024-06-06 14:39 ` dpdklab
2024-06-06 14:40 ` dpdklab
2024-06-06 14:40 ` dpdklab
2024-06-06 14:41 ` dpdklab
2024-06-06 14:45 ` dpdklab
2024-06-06 14:45 ` dpdklab
2024-06-06 14:45 ` dpdklab
2024-06-06 14:46 ` dpdklab
2024-06-06 14:48 ` dpdklab
2024-06-06 14:48 ` dpdklab
2024-06-06 14:49 ` dpdklab
2024-06-06 14:49 ` dpdklab
2024-06-06 14:53 ` dpdklab
2024-06-06 14:53 ` dpdklab
2024-06-06 14:54 ` dpdklab
2024-06-06 14:59 ` dpdklab
2024-06-06 15:00 ` |FAILURE| " dpdklab
2024-06-06 15:01 ` dpdklab
2024-06-06 15:03 ` |SUCCESS| " dpdklab
2024-06-06 15:03 ` dpdklab
2024-06-06 15:06 ` |FAILURE| " dpdklab
2024-06-06 15:21 ` |SUCCESS| " dpdklab
2024-06-06 15:24 ` dpdklab
2024-06-06 15:26 ` dpdklab [this message]
2024-06-06 15:26 ` dpdklab
2024-06-06 15:31 ` dpdklab
2024-06-06 15:33 ` dpdklab
2024-06-06 15:33 ` dpdklab
2024-06-06 15:33 ` dpdklab
2024-06-06 15:34 ` dpdklab
2024-06-06 15:39 ` dpdklab
2024-06-06 15:40 ` dpdklab
2024-06-06 15:42 ` dpdklab
2024-06-06 15:43 ` dpdklab
2024-06-06 15:45 ` dpdklab
2024-06-06 15:45 ` dpdklab
2024-06-06 15:47 ` dpdklab
2024-06-06 15:49 ` dpdklab
2024-06-06 15:49 ` dpdklab
2024-06-06 15:50 ` dpdklab
2024-06-06 15:50 ` dpdklab
2024-06-06 15:53 ` dpdklab
2024-06-06 15:53 ` dpdklab
2024-06-06 15:53 ` dpdklab
2024-06-06 15:53 ` |FAILURE| " dpdklab
2024-06-06 15:54 ` |SUCCESS| " dpdklab
2024-06-06 15:59 ` dpdklab
2024-06-06 15:59 ` dpdklab
2024-06-06 16:01 ` |FAILURE| " dpdklab
2024-06-06 16:02 ` |SUCCESS| " dpdklab
2024-06-06 16:05 ` |FAILURE| " dpdklab
2024-06-06 16:08 ` dpdklab
2024-06-06 16:09 ` dpdklab
2024-06-06 16:10 ` dpdklab
2024-06-06 16:19 ` |SUCCESS| " dpdklab
2024-06-06 16:26 ` dpdklab
2024-06-06 16:28 ` dpdklab
2024-06-06 16:30 ` dpdklab
2024-06-06 16:30 ` dpdklab
2024-06-06 16:31 ` dpdklab
2024-06-06 16:31 ` dpdklab
2024-06-06 16:33 ` dpdklab
2024-06-06 16:34 ` dpdklab
2024-06-06 16:37 ` dpdklab
2024-06-06 16:46 ` dpdklab
2024-06-06 16:47 ` dpdklab
2024-06-06 16:47 ` dpdklab
2024-06-06 16:48 ` dpdklab
2024-06-06 17:21 ` dpdklab
2024-06-06 17:21 ` dpdklab
2024-06-06 17:24 ` dpdklab
2024-06-06 17:26 ` dpdklab
2024-06-06 18:10 ` 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=6661d51b.050a0220.34fbe8.56ebSMTPIN_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).