From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138413-138420 [PATCH] [v3,8/8] crypto/cnxk: update the c
Date: Fri, 15 Mar 2024 00:58:57 -0700 (PDT) [thread overview]
Message-ID: <65f3ffc1.4a0a0220.33ae2.596aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240315054213.540-9-vvelumuri@marvell.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138420
_Testing PASS_
Submitter: Vidya Sagar Velumuri <vvelumuri@marvell.com>
Date: Friday, March 15 2024 05:42:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3
138413-138420 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian 12 (arm) | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29568/
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-03-15 7:58 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240315054213.540-9-vvelumuri@marvell.com>
2024-03-15 5:21 ` |SUCCESS| pw138413-138420 [PATCH v3 8/8] crypto/cnxk: update the context structure of tls qemudev
2024-03-15 5:26 ` qemudev
2024-03-15 5:46 ` |SUCCESS| pw138420 " checkpatch
2024-03-15 6:43 ` |SUCCESS| pw138413-138420 [PATCH] [v3,8/8] crypto/cnxk: update the c dpdklab
2024-03-15 6:43 ` |SUCCESS| pw138420 [PATCH v3 8/8] crypto/cnxk: update the context structure of tls 0-day Robot
2024-03-15 6:54 ` |SUCCESS| pw138413-138420 [PATCH] [v3,8/8] crypto/cnxk: update the c dpdklab
2024-03-15 7:00 ` dpdklab
2024-03-15 7:01 ` dpdklab
2024-03-15 7:01 ` dpdklab
2024-03-15 7:02 ` dpdklab
2024-03-15 7:02 ` dpdklab
2024-03-15 7:02 ` dpdklab
2024-03-15 7:02 ` dpdklab
2024-03-15 7:03 ` dpdklab
2024-03-15 7:03 ` dpdklab
2024-03-15 7:03 ` dpdklab
2024-03-15 7:04 ` dpdklab
2024-03-15 7:04 ` dpdklab
2024-03-15 7:06 ` dpdklab
2024-03-15 7:06 ` dpdklab
2024-03-15 7:07 ` dpdklab
2024-03-15 7:07 ` dpdklab
2024-03-15 7:08 ` dpdklab
2024-03-15 7:08 ` dpdklab
2024-03-15 7:08 ` dpdklab
2024-03-15 7:08 ` dpdklab
2024-03-15 7:10 ` dpdklab
2024-03-15 7:10 ` dpdklab
2024-03-15 7:11 ` dpdklab
2024-03-15 7:12 ` dpdklab
2024-03-15 7:12 ` dpdklab
2024-03-15 7:14 ` dpdklab
2024-03-15 7:14 ` dpdklab
2024-03-15 7:15 ` dpdklab
2024-03-15 7:16 ` dpdklab
2024-03-15 7:16 ` dpdklab
2024-03-15 7:16 ` dpdklab
2024-03-15 7:16 ` dpdklab
2024-03-15 7:17 ` dpdklab
2024-03-15 7:17 ` dpdklab
2024-03-15 7:17 ` dpdklab
2024-03-15 7:18 ` dpdklab
2024-03-15 7:18 ` dpdklab
2024-03-15 7:18 ` dpdklab
2024-03-15 7:18 ` dpdklab
2024-03-15 7:19 ` dpdklab
2024-03-15 7:19 ` dpdklab
2024-03-15 7:19 ` dpdklab
2024-03-15 7:20 ` dpdklab
2024-03-15 7:20 ` dpdklab
2024-03-15 7:20 ` dpdklab
2024-03-15 7:20 ` dpdklab
2024-03-15 7:21 ` dpdklab
2024-03-15 7:22 ` dpdklab
2024-03-15 7:23 ` dpdklab
2024-03-15 7:44 ` dpdklab
2024-03-15 7:46 ` dpdklab
2024-03-15 7:47 ` dpdklab
2024-03-15 7:47 ` dpdklab
2024-03-15 7:49 ` dpdklab
2024-03-15 7:51 ` dpdklab
2024-03-15 7:52 ` dpdklab
2024-03-15 7:53 ` dpdklab
2024-03-15 7:53 ` dpdklab
2024-03-15 7:54 ` dpdklab
2024-03-15 7:54 ` dpdklab
2024-03-15 7:55 ` dpdklab
2024-03-15 7:58 ` dpdklab
2024-03-15 7:58 ` dpdklab [this message]
2024-03-15 7:59 ` dpdklab
2024-03-15 8:00 ` dpdklab
2024-03-15 8:00 ` dpdklab
2024-03-15 8:01 ` dpdklab
2024-03-15 8:02 ` dpdklab
2024-03-15 8:04 ` dpdklab
2024-03-15 8:05 ` dpdklab
2024-03-15 8:41 ` dpdklab
2024-03-15 9:23 ` dpdklab
2024-03-19 0:31 ` dpdklab
2024-03-19 1:08 ` 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=65f3ffc1.4a0a0220.33ae2.596aSMTPIN_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).