From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141434-141445 [PATCH] [12/12] crypto/cnxk: enable dual s
Date: Thu, 20 Jun 2024 16:13:02 -0700 (PDT) [thread overview]
Message-ID: <6674b77e.050a0220.72fc.12b8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240620145848.3461844-13-asasidharan@marvell.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141445
_Testing PASS_
Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Thursday, June 20 2024 14:58:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f
141434-141445 --> testing pass
Test environment and result as below:
+---------------------+--------------------+-------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+===================+======================+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2022 | PASS | PASS | PASS |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2019 | PASS | SKIPPED | PASS |
+---------------------+--------------------+-------------------+----------------------+
| FreeBSD 14.1 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------------+
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30264/
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-20 23:13 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240620145848.3461844-13-asasidharan@marvell.com>
2024-06-20 14:34 ` |SUCCESS| pw141434-141445 [PATCH 12/12] crypto/cnxk: enable dual submission to CPT qemudev
2024-06-20 14:39 ` qemudev
2024-06-20 15:02 ` |SUCCESS| pw141445 " checkpatch
2024-06-20 16:07 ` 0-day Robot
2024-06-20 19:51 ` |SUCCESS| pw141434-141445 [PATCH] [12/12] crypto/cnxk: enable dual s dpdklab
2024-06-20 19:51 ` dpdklab
2024-06-20 19:55 ` dpdklab
2024-06-20 19:58 ` dpdklab
2024-06-20 20:08 ` dpdklab
2024-06-20 20:11 ` dpdklab
2024-06-20 20:13 ` dpdklab
2024-06-20 20:16 ` dpdklab
2024-06-20 20:17 ` dpdklab
2024-06-20 20:20 ` dpdklab
2024-06-20 20:21 ` dpdklab
2024-06-20 20:28 ` dpdklab
2024-06-20 20:29 ` dpdklab
2024-06-20 20:30 ` dpdklab
2024-06-20 20:32 ` dpdklab
2024-06-20 20:51 ` dpdklab
2024-06-20 21:04 ` dpdklab
2024-06-20 21:37 ` dpdklab
2024-06-20 21:37 ` dpdklab
2024-06-20 21:38 ` dpdklab
2024-06-20 22:02 ` dpdklab
2024-06-20 22:11 ` dpdklab
2024-06-20 22:12 ` dpdklab
2024-06-20 22:13 ` dpdklab
2024-06-20 22:16 ` dpdklab
2024-06-20 22:24 ` dpdklab
2024-06-20 22:24 ` dpdklab
2024-06-20 22:27 ` dpdklab
2024-06-20 22:27 ` dpdklab
2024-06-20 22:31 ` dpdklab
2024-06-20 22:33 ` dpdklab
2024-06-20 22:45 ` dpdklab
2024-06-20 23:05 ` dpdklab
2024-06-20 23:09 ` dpdklab
2024-06-20 23:09 ` dpdklab
2024-06-20 23:10 ` dpdklab
2024-06-20 23:10 ` dpdklab
2024-06-20 23:11 ` dpdklab
2024-06-20 23:13 ` dpdklab [this message]
2024-06-20 23:13 ` dpdklab
2024-06-20 23:42 ` dpdklab
2024-06-20 23:45 ` dpdklab
2024-06-20 23:49 ` dpdklab
2024-06-20 23:50 ` dpdklab
2024-06-20 23:52 ` dpdklab
2024-06-21 0:01 ` dpdklab
2024-06-21 0:05 ` dpdklab
2024-06-21 0:05 ` dpdklab
2024-06-21 0:09 ` dpdklab
2024-06-21 0:09 ` |FAILURE| " dpdklab
2024-06-21 0:09 ` |SUCCESS| " dpdklab
2024-06-21 0:11 ` |FAILURE| " dpdklab
2024-06-21 0:16 ` |SUCCESS| " dpdklab
2024-06-21 0:18 ` dpdklab
2024-06-21 0:19 ` dpdklab
2024-06-21 0:20 ` dpdklab
2024-06-21 0:21 ` dpdklab
2024-06-21 0:27 ` dpdklab
2024-06-21 0:30 ` dpdklab
2024-06-21 0:35 ` |FAILURE| " dpdklab
2024-06-21 0:38 ` |SUCCESS| " dpdklab
2024-06-21 0:40 ` |FAILURE| " dpdklab
2024-06-21 0:40 ` |SUCCESS| " dpdklab
2024-06-21 0:44 ` dpdklab
2024-06-21 0:45 ` dpdklab
2024-06-21 0:46 ` dpdklab
2024-06-21 0:46 ` dpdklab
2024-06-21 0:46 ` dpdklab
2024-06-21 0:47 ` |FAILURE| " dpdklab
2024-06-21 0:47 ` |SUCCESS| " dpdklab
2024-06-21 0:48 ` |FAILURE| " dpdklab
2024-06-21 0:48 ` |SUCCESS| " dpdklab
2024-06-21 0:49 ` dpdklab
2024-06-21 0:50 ` dpdklab
2024-06-21 0:50 ` dpdklab
2024-06-21 0:50 ` |FAILURE| " dpdklab
2024-06-21 0:51 ` |SUCCESS| " dpdklab
2024-06-21 0:51 ` dpdklab
2024-06-21 0:52 ` dpdklab
2024-06-21 0:52 ` |FAILURE| " dpdklab
2024-06-21 0:54 ` dpdklab
2024-06-21 1:04 ` |SUCCESS| " dpdklab
2024-06-21 1:04 ` |FAILURE| " dpdklab
2024-06-21 1:04 ` |SUCCESS| " dpdklab
2024-06-21 1:04 ` |FAILURE| " dpdklab
2024-06-21 1:04 ` dpdklab
2024-06-21 1:11 ` |SUCCESS| " dpdklab
2024-06-21 1:12 ` |FAILURE| " dpdklab
2024-06-21 1:13 ` dpdklab
2024-06-21 1:15 ` dpdklab
2024-06-21 1:16 ` dpdklab
2024-06-21 1:25 ` dpdklab
2024-06-21 1:26 ` dpdklab
2024-06-21 1:36 ` dpdklab
2024-06-21 1:49 ` dpdklab
2024-06-21 2:06 ` dpdklab
2024-06-21 2:06 ` dpdklab
2024-06-21 2:32 ` dpdklab
2024-06-21 2:37 ` dpdklab
2024-06-21 2:38 ` dpdklab
2024-06-21 2:42 ` dpdklab
2024-06-21 2:45 ` dpdklab
2024-06-21 2:45 ` dpdklab
2024-06-21 2:46 ` dpdklab
2024-06-21 2:47 ` dpdklab
2024-06-21 2:54 ` dpdklab
2024-06-21 2:54 ` dpdklab
2024-06-21 3:07 ` dpdklab
2024-06-21 3:15 ` dpdklab
2024-06-21 3:36 ` dpdklab
2024-06-21 15:25 ` |SUCCESS| " dpdklab
2024-06-21 15:43 ` dpdklab
2024-06-22 7:48 ` 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=6674b77e.050a0220.72fc.12b8SMTPIN_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).