From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141159 [PATCH] crypto/cnxk: fix coverity issues
Date: Mon, 17 Jun 2024 13:05:39 -0700 (PDT) [thread overview]
Message-ID: <66709713.050a0220.ca7b5.b7b4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240615113304.2197-1-gmuthukrishn@marvell.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141159
_Testing PASS_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Saturday, June 15 2024 11:33:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6909b48776badc05542a410ebd34bcfec4c248bf
141159 --> testing pass
Test environment and result as below:
+---------------------+-------------------+--------------------+----------------------+
| Environment | dpdk_msvc_compile | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+===================+====================+======================+
| Windows Server 2022 | PASS | PASS | PASS |
+---------------------+-------------------+--------------------+----------------------+
| FreeBSD 13.3 | SKIPPED | PASS | SKIPPED |
+---------------------+-------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED | PASS | SKIPPED |
+---------------------+-------------------+--------------------+----------------------+
| FreeBSD 14.1 | SKIPPED | PASS | SKIPPED |
+---------------------+-------------------+--------------------+----------------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
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/30197/
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-17 20:05 UTC|newest]
Thread overview: 210+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240615113304.2197-1-gmuthukrishn@marvell.com>
2024-06-15 11:24 ` qemudev
2024-06-15 11:28 ` qemudev
2024-06-15 11:34 ` checkpatch
2024-06-15 12:25 ` 0-day Robot
2024-06-15 12:53 ` dpdklab
2024-06-15 12:53 ` dpdklab
2024-06-15 13:00 ` dpdklab
2024-06-15 13:13 ` dpdklab
2024-06-15 13:14 ` dpdklab
2024-06-15 13:14 ` dpdklab
2024-06-15 13:15 ` dpdklab
2024-06-15 13:15 ` dpdklab
2024-06-15 13:16 ` dpdklab
2024-06-15 13:16 ` dpdklab
2024-06-15 13:17 ` dpdklab
2024-06-15 13:17 ` dpdklab
2024-06-15 13:17 ` dpdklab
2024-06-15 13:24 ` dpdklab
2024-06-15 13:26 ` dpdklab
2024-06-15 13:38 ` dpdklab
2024-06-15 13:39 ` dpdklab
2024-06-15 13:44 ` dpdklab
2024-06-15 13:46 ` dpdklab
2024-06-15 13:46 ` dpdklab
2024-06-15 13:48 ` dpdklab
2024-06-15 13:50 ` dpdklab
2024-06-15 13:55 ` dpdklab
2024-06-15 13:55 ` dpdklab
2024-06-15 13:59 ` dpdklab
2024-06-15 14:00 ` dpdklab
2024-06-15 14:00 ` dpdklab
2024-06-15 14:01 ` dpdklab
2024-06-15 14:01 ` dpdklab
2024-06-15 14:01 ` dpdklab
2024-06-15 14:01 ` dpdklab
2024-06-15 14:02 ` dpdklab
2024-06-15 14:02 ` dpdklab
2024-06-15 14:02 ` dpdklab
2024-06-15 14:02 ` dpdklab
2024-06-15 14:03 ` dpdklab
2024-06-15 14:13 ` dpdklab
2024-06-15 14:18 ` dpdklab
2024-06-15 14:19 ` dpdklab
2024-06-15 14:21 ` dpdklab
2024-06-15 14:23 ` dpdklab
2024-06-15 14:24 ` dpdklab
2024-06-15 14:24 ` dpdklab
2024-06-15 14:25 ` dpdklab
2024-06-15 14:26 ` dpdklab
2024-06-15 14:26 ` dpdklab
2024-06-15 14:27 ` dpdklab
2024-06-15 14:27 ` dpdklab
2024-06-15 14:27 ` dpdklab
2024-06-15 14:27 ` dpdklab
2024-06-15 14:28 ` dpdklab
2024-06-15 14:28 ` dpdklab
2024-06-15 14:28 ` dpdklab
2024-06-15 14:28 ` dpdklab
2024-06-15 14:29 ` dpdklab
2024-06-15 14:29 ` dpdklab
2024-06-15 14:29 ` dpdklab
2024-06-15 14:29 ` dpdklab
2024-06-15 14:29 ` dpdklab
2024-06-15 14:30 ` dpdklab
2024-06-15 14:30 ` dpdklab
2024-06-15 14:30 ` dpdklab
2024-06-15 14:30 ` dpdklab
2024-06-15 14:31 ` dpdklab
2024-06-15 14:31 ` dpdklab
2024-06-15 14:31 ` dpdklab
2024-06-15 14:32 ` dpdklab
2024-06-15 14:32 ` dpdklab
2024-06-15 14:32 ` dpdklab
2024-06-15 14:32 ` dpdklab
2024-06-15 14:33 ` dpdklab
2024-06-15 14:33 ` dpdklab
2024-06-15 14:33 ` dpdklab
2024-06-15 14:34 ` dpdklab
2024-06-15 14:34 ` dpdklab
2024-06-15 14:35 ` dpdklab
2024-06-15 14:35 ` dpdklab
2024-06-15 14:36 ` dpdklab
2024-06-15 14:36 ` dpdklab
2024-06-15 14:36 ` dpdklab
2024-06-15 14:36 ` dpdklab
2024-06-15 14:37 ` dpdklab
2024-06-15 14:37 ` dpdklab
2024-06-15 14:37 ` dpdklab
2024-06-15 14:37 ` dpdklab
2024-06-15 14:37 ` dpdklab
2024-06-15 14:38 ` dpdklab
2024-06-15 14:38 ` dpdklab
2024-06-15 14:38 ` dpdklab
2024-06-15 14:39 ` dpdklab
2024-06-15 14:41 ` dpdklab
2024-06-15 14:43 ` dpdklab
2024-06-15 14:44 ` dpdklab
2024-06-15 14:45 ` dpdklab
2024-06-15 14:54 ` dpdklab
2024-06-15 14:55 ` dpdklab
2024-06-15 14:55 ` dpdklab
2024-06-15 14:55 ` dpdklab
2024-06-15 14:56 ` dpdklab
2024-06-15 14:57 ` dpdklab
2024-06-15 14:59 ` dpdklab
2024-06-15 15:05 ` dpdklab
2024-06-15 15:07 ` dpdklab
2024-06-15 15:10 ` dpdklab
2024-06-15 15:13 ` dpdklab
2024-06-15 15:17 ` dpdklab
2024-06-15 15:23 ` |WARNING| " dpdklab
2024-06-15 17:10 ` |SUCCESS| " dpdklab
2024-06-15 17:10 ` dpdklab
2024-06-15 18:07 ` dpdklab
2024-06-17 20:02 ` dpdklab
2024-06-17 20:03 ` dpdklab
2024-06-17 20:03 ` dpdklab
2024-06-17 20:03 ` dpdklab
2024-06-17 20:03 ` dpdklab
2024-06-17 20:04 ` dpdklab
2024-06-17 20:04 ` dpdklab
2024-06-17 20:05 ` dpdklab
2024-06-17 20:05 ` dpdklab [this message]
2024-06-17 20:06 ` dpdklab
2024-06-17 20:06 ` dpdklab
2024-06-17 20:06 ` dpdklab
2024-06-17 20:07 ` dpdklab
2024-06-17 20:07 ` dpdklab
2024-06-17 20:09 ` dpdklab
2024-06-17 20:10 ` dpdklab
2024-06-17 20:11 ` dpdklab
2024-06-17 20:11 ` dpdklab
2024-06-17 20:16 ` dpdklab
2024-06-17 20:32 ` dpdklab
2024-06-17 20:39 ` dpdklab
2024-06-17 20:39 ` dpdklab
2024-06-17 20:47 ` dpdklab
2024-06-17 20:49 ` dpdklab
2024-06-17 20:58 ` dpdklab
2024-06-17 20:59 ` dpdklab
2024-06-17 21:04 ` dpdklab
2024-06-17 21:05 ` dpdklab
2024-06-17 21:38 ` dpdklab
2024-06-17 21:39 ` dpdklab
2024-06-17 21:39 ` dpdklab
2024-06-17 21:40 ` dpdklab
2024-06-17 21:47 ` dpdklab
2024-06-17 21:59 ` dpdklab
2024-06-17 21:59 ` dpdklab
2024-06-17 22:00 ` dpdklab
2024-06-17 22:04 ` dpdklab
2024-06-17 22:22 ` dpdklab
2024-06-17 22:28 ` dpdklab
2024-06-17 22:29 ` dpdklab
2024-06-17 22:32 ` dpdklab
2024-06-17 22:33 ` dpdklab
2024-06-17 22:39 ` dpdklab
2024-06-17 22:44 ` dpdklab
2024-06-17 22:56 ` dpdklab
2024-06-17 22:56 ` dpdklab
2024-06-17 22:59 ` dpdklab
2024-06-17 23:12 ` dpdklab
2024-06-17 23:13 ` dpdklab
2024-06-17 23:15 ` dpdklab
2024-06-17 23:17 ` dpdklab
2024-06-17 23:17 ` dpdklab
2024-06-17 23:18 ` dpdklab
2024-06-17 23:19 ` dpdklab
2024-06-17 23:20 ` dpdklab
2024-06-17 23:21 ` dpdklab
2024-06-17 23:22 ` dpdklab
2024-06-17 23:29 ` dpdklab
2024-06-17 23:29 ` dpdklab
2024-06-17 23:30 ` dpdklab
2024-06-17 23:30 ` dpdklab
2024-06-17 23:31 ` dpdklab
2024-06-17 23:31 ` dpdklab
2024-06-17 23:32 ` dpdklab
2024-06-17 23:32 ` dpdklab
2024-06-17 23:35 ` dpdklab
2024-06-17 23:36 ` dpdklab
2024-06-17 23:37 ` dpdklab
2024-06-17 23:38 ` dpdklab
2024-06-17 23:39 ` dpdklab
2024-06-17 23:39 ` dpdklab
2024-06-17 23:41 ` dpdklab
2024-06-17 23:42 ` dpdklab
2024-06-17 23:43 ` dpdklab
2024-06-17 23:48 ` dpdklab
2024-06-17 23:49 ` dpdklab
2024-06-17 23:50 ` dpdklab
2024-06-17 23:51 ` dpdklab
2024-06-17 23:52 ` dpdklab
2024-06-17 23:53 ` dpdklab
2024-06-17 23:54 ` dpdklab
2024-06-18 0:09 ` dpdklab
2024-06-18 0:13 ` dpdklab
2024-06-18 0:15 ` dpdklab
2024-06-18 0:16 ` dpdklab
2024-06-18 0:17 ` dpdklab
2024-06-18 0:17 ` dpdklab
2024-06-18 0:18 ` dpdklab
2024-06-18 0:19 ` dpdklab
2024-06-18 0:20 ` dpdklab
2024-06-18 0:20 ` dpdklab
2024-06-18 0:24 ` dpdklab
2024-06-18 0:27 ` dpdklab
2024-06-18 0:33 ` dpdklab
2024-06-18 1:09 ` dpdklab
2024-06-18 1:32 ` 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=66709713.050a0220.ca7b5.b7b4SMTPIN_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).