From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135904-135927 [PATCH] [v3,24/24] crypto/cnxk: add CPT SG
Date: Wed, 17 Jan 2024 20:35:07 -0800 (PST) [thread overview]
Message-ID: <65a8aa7b.050a0220.629ee.f732SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135927
_Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Wednesday, January 17 2024 10:31:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a
135904-135927 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28882/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-18 4:35 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 4:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-18 12:12 dpdklab
2024-01-18 6:48 dpdklab
2024-01-18 6:46 dpdklab
2024-01-18 6:44 dpdklab
2024-01-18 6:28 dpdklab
2024-01-18 5:45 dpdklab
2024-01-18 5:31 dpdklab
2024-01-18 5:10 dpdklab
2024-01-18 4:54 dpdklab
2024-01-18 4:45 dpdklab
2024-01-18 4:43 dpdklab
2024-01-18 4:41 dpdklab
2024-01-18 4:36 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:32 dpdklab
2024-01-18 4:31 dpdklab
2024-01-18 4:31 dpdklab
2024-01-18 4:31 dpdklab
2024-01-18 4:31 dpdklab
2024-01-18 4:29 dpdklab
2024-01-18 4:28 dpdklab
2024-01-18 4:27 dpdklab
2024-01-18 4:27 dpdklab
2024-01-18 4:26 dpdklab
2024-01-18 4:26 dpdklab
2024-01-18 4:26 dpdklab
2024-01-18 4:23 dpdklab
2024-01-18 4:23 dpdklab
2024-01-18 4:22 dpdklab
2024-01-18 4:22 dpdklab
2024-01-18 4:17 dpdklab
2024-01-18 4:17 dpdklab
2024-01-18 4:16 dpdklab
2024-01-18 4:15 dpdklab
2024-01-18 4:13 dpdklab
2024-01-18 4:13 dpdklab
2024-01-18 3:56 dpdklab
2024-01-18 3:55 dpdklab
2024-01-18 3:54 dpdklab
2024-01-18 3:53 dpdklab
2024-01-18 3:52 dpdklab
2024-01-18 3:51 dpdklab
2024-01-18 3:50 dpdklab
2024-01-18 3:49 dpdklab
2024-01-18 3:46 dpdklab
2024-01-18 3:43 dpdklab
2024-01-18 3:43 dpdklab
2024-01-18 3:42 dpdklab
2024-01-18 3:41 dpdklab
2024-01-18 3:41 dpdklab
2024-01-18 3:34 dpdklab
2024-01-18 3:33 dpdklab
2024-01-18 3:12 dpdklab
2024-01-18 3:06 dpdklab
2024-01-18 3:06 dpdklab
2024-01-18 3:05 dpdklab
2024-01-18 2:55 dpdklab
2024-01-18 2:54 dpdklab
2024-01-18 2:54 dpdklab
2024-01-18 2:54 dpdklab
2024-01-18 2:51 dpdklab
2024-01-18 2:50 dpdklab
2024-01-18 2:50 dpdklab
2024-01-18 2:47 dpdklab
2024-01-18 2:46 dpdklab
2024-01-18 2:45 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=65a8aa7b.050a0220.629ee.f732SMTPIN_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).