From: sys_stv@intel.com
To: test-report@dpdk.org, thomas@monjalon.net
Cc: dpdk_sw_eng@intel.com, npg.sw.core.tools.prc@intel.com
Subject: |SUCCESS| dpdk-next-crypto| 7df61db6c3| Intel-compilation
Date: 28 Dec 2024 13:44:24 -0800 [thread overview]
Message-ID: <ab3bf2$304h5k@fmviesa010-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5123 bytes --]
Test-Label: Intel-compilation
Test-Status: SUCCESS
_Compilation OK_
commit 7df61db6c387703a36306c1aea92225921e2eeb2
Author: David Marchand <david.marchand@redhat.com>
Date: Tue Dec 3 08:54:45 2024 +0100
version: 25.03-rc0
DPDK git Repo: dpdk-next-crypto
Meson Build Summary: 25 Builds Done, 25 Successful, 0 Failures, 0 Blocked
+------------------+------------+--------------+------------+------------+-----------+----------+------------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+------------------+------------+--------------+------------+------------+-----------+----------+------------+
| OpenAnolis8.9-64 | pass | | | | | | |
| FreeBSD14-64 | pass | pass | | pass | pass | | |
| RHEL94-64 | pass | pass | | pass | pass | | |
| SUSE15-64 | pass | pass | | | | | |
| AzureLinux3.0-64 | pass | | | | | | |
| UB2404-32 | pass | | | | | | |
| RHEL8.10-64 | pass | | | | | | |
| UB2404-64N | pass | | | pass | | | |
| UB2404-64 | pass | pass | | | | pass | pass |
| RHEL94-64Rt | pass | | | | | | |
| UB2410-64 | pass | | | | | | |
| FC40-64 | pass | pass | | | | | |
| UB2404-64Rt | pass | | | | | | |
+------------------+------------+--------------+------------+------------+-----------+----------+------------+
Comments:
Because of DPDK bug (https://bugs.dpdk.org/show_bug.cgi?id=928),
All the dpdk-next-* branch add `Ddisable_drivers=event/cnxk` option when build with ICC complier.
Test environment and configuration as below:
OS: OpenAnolis8.9-64
Kernel Version: 5.10.134-16.2.an8.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Anolis 8.5.0-22.0.1)
Clang Version: 15.0.7 (Anolis 15.0.7-1.0.3.module+an8.8.0+11135+e398acfc)
x86_64-native-linuxapp-gcc
OS: FreeBSD14-64
Kernel Version: 14.1-RELEASE
GCC Version: gcc (FreeBSD Ports Collection) 13.2.0
Clang Version: 18.1.5 (https://github.com/llvm/llvm-project.git llvmorg-18.1.5-0-g617a15a9eac9)
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc+debug
OS: RHEL94-64
Kernel Version: 5.14.0-427.13.1.el9_4.x86_64
GCC Version: gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
Clang Version: 17.0.6 (Red Hat, Inc. 17.0.6-5.el9)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc+shared
x86_64-native-linuxapp-gcc+debug
OS: SUSE15-64
Kernel Version: 6.4.0-150600.21-default
GCC Version: gcc (SUSE Linux) 7.5.0
Clang Version: 17.0.6
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
OS: AzureLinux3.0-64
Kernel Version: 6.6.47.1-1.azl3
GCC Version: gcc (GCC) 13.2.0
Clang Version: 18.1.2
x86_64-native-linuxapp-gcc
OS: UB2404-32
Kernel Version: 6.8.0-41-generic
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: NA
i686-native-linuxapp-gcc
OS: RHEL8.10-64
Kernel Version: 4.18.0-553.el8_10.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-21)
Clang Version: 17.0.6 (Red Hat 17.0.6-1.module+el8.10.0+20808+e12784c0)
x86_64-native-linuxapp-gcc
OS: UB2404-64N
Kernel Version: 6.10.8-061008-generic
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc+shared
OS: UB2404-64
Kernel Version: 6.8.0-41-generic
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc+16byte
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-doc
OS: RHEL94-64Rt
Kernel Version: 5.14.0-427.13.1.el9_4.x86_64+rt
GCC Version: gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
Clang Version: 17.0.6 (Red Hat, Inc. 17.0.6-5.el9)
x86_64-native-linuxapp-gcc
OS: UB2410-64
Kernel Version: 6.11.0-8-generic
GCC Version: gcc (Ubuntu 14.2.0-4ubuntu2) 14.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc
OS: FC40-64
Kernel Version: 6.8.5-301.fc40.x86_64
GCC Version: gcc (GCC) 14.0.1 20240411 (Red Hat 14.0.1-0)
Clang Version: 18.1.1 (Fedora 18.1.1-1.fc40)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: UB2404-64Rt
Kernel Version: 6.8.0-rt8
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc
DPDK STV team
next reply other threads:[~2024-12-28 21:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 21:44 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-29 21:43 sys_stv
2024-12-27 21:37 sys_stv
2024-12-26 21:48 sys_stv
2024-12-25 21:40 sys_stv
2024-12-24 21:40 sys_stv
2024-12-23 21:52 sys_stv
2024-12-19 21:40 sys_stv
2024-12-18 21:41 sys_stv
2024-12-17 21:40 sys_stv
2024-12-16 21:42 sys_stv
2024-12-15 21:39 sys_stv
2024-12-14 21:42 sys_stv
2024-12-13 21:39 sys_stv
2024-12-12 21:41 sys_stv
2024-12-11 21:41 sys_stv
2024-12-10 21:50 sys_stv
2024-12-09 21:45 sys_stv
2024-12-08 21:40 sys_stv
2024-12-07 21:39 sys_stv
2024-12-06 21:41 sys_stv
2024-12-05 21:46 sys_stv
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='ab3bf2$304h5k@fmviesa010-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dpdk_sw_eng@intel.com \
--cc=npg.sw.core.tools.prc@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).