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-eventdev| e2e546ab5b| Intel-compilation
Date: 12 Apr 2024 14:36:45 -0700 [thread overview]
Message-ID: <7f45a9$omadc@fmviesa003-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5526 bytes --]
Test-Label: Intel-compilation
Test-Status: SUCCESS
_Compilation OK_
commit e2e546ab5bf5e024986ccb5310ab43982f3bb40c
Author: David Marchand <david.marchand@redhat.com>
Date: Sat Mar 30 18:12:32 2024 +0100
version: 24.07-rc0
DPDK git Repo: dpdk-next-eventdev
Meson Build Summary: 26 Builds Done, 26 Successful, 0 Failures, 0 Blocked
+-------------------+------------+--------------+------------+------------+-----------+----------+------------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+-------------------+------------+--------------+------------+------------+-----------+----------+------------+
| OpenAnolis8.8-64 | pass | | | | | | |
| FreeBSD14-64 | pass | pass | | pass | pass | | |
| RHEL92-64 | pass | pass | | pass | pass | | |
| SUSE15-64 | pass | pass | | | | | |
| CBL-Mariner2.0-64 | pass | | | | | | |
| UB2204-32 | pass | | | | | | |
| RHEL89-64 | pass | | | | | | |
| UB2204-64N | pass | | | pass | | | |
| UB2204-64 | pass | pass | | | | pass | pass |
| CentOS79-64 | pass | | | | | | |
| RHEL92-64Rt | pass | | | | | | |
| UB2310-64 | pass | | | | | | |
| FC39-64 | pass | pass | | | | | |
| UB2204-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.8-64
Kernel Version: 5.10.134-13.an8.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Anolis 8.5.0-10.0.3)
Clang Version: 13.0.1 (Anolis 13.0.1-2.0.2.module+an8.7.0+10996+1588f068)
x86_64-native-linuxapp-gcc
OS: FreeBSD14-64
Kernel Version: 14.0-RELEASE
GCC Version: gcc (FreeBSD Ports Collection) 12.2.0
Clang Version: 16.0.6 (https://github.com/llvm/llvm-project.git llvmorg-16.0.6-0-g7cbf1a259152)
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc+debug
OS: RHEL92-64
Kernel Version: 5.14.0-284.11.1.el9_2.x86_64
GCC Version: gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4)
Clang Version: 15.0.7 (Red Hat 15.0.7-2.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: 5.14.21-150500.53-default
GCC Version: gcc (SUSE Linux) 7.5.0
Clang Version: 15.0.7
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
OS: CBL-Mariner2.0-64
Kernel Version: 5.15.55.1_2e9a4f9+
GCC Version: gcc (GCC) 11.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc
OS: UB2204-32
Kernel Version: 5.15.0-58-generic
GCC Version: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang Version: NA
i686-native-linuxapp-gcc
OS: RHEL89-64
Kernel Version: 4.18.0-513.5.1.el8_9.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-20)
Clang Version: 16.0.6 (Red Hat 16.0.6-2.module+el8.9.0+19521+190d7aba)
x86_64-native-linuxapp-gcc
OS: UB2204-64N
Kernel Version: 6.2.13-060213-generic
GCC Version: gcc (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
Clang Version: 14.0.0-1ubuntu1.1
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc+shared
OS: UB2204-64
Kernel Version: 5.15.0-58-generic
GCC Version: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang Version: 14.0.0-1ubuntu1.1
x86_64-native-linuxapp-gcc+16byte
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-doc
OS: CentOS79-64
Kernel Version: 3.10.0-1160.81.1.el7.x86_64
GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-gcc
OS: RHEL92-64Rt
Kernel Version: 5.14.0-284.11.1.rt14.296.el9_2.x86_64
GCC Version: gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4)
Clang Version: 15.0.7 (Red Hat 15.0.7-2.el9)
x86_64-native-linuxapp-gcc
OS: UB2310-64
Kernel Version: 6.5.0-9-generic
GCC Version: gcc (Ubuntu 13.2.0-4ubuntu3) 13.2.0
Clang Version: NA
x86_64-native-linuxapp-gcc
OS: FC39-64
Kernel Version: 6.5.6-300.fc39.x86_64
GCC Version: gcc (GCC) 13.2.1 20230918 (Red Hat 13.2.1-3)
Clang Version: 17.0.6 (Fedora 17.0.6-1.fc39)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: UB2204-64Rt
Kernel Version: 5.17.5-051705-generic
GCC Version: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang Version: 14.0.0-1ubuntu1.1
x86_64-native-linuxapp-gcc
DPDK STV team
next reply other threads:[~2024-04-12 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 21:36 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-21 21:36 sys_stv
2024-04-20 21:38 sys_stv
2024-04-19 21:36 sys_stv
2024-04-18 21:36 sys_stv
2024-04-17 21:38 sys_stv
2024-04-16 21:39 sys_stv
2024-04-15 21:38 sys_stv
2024-04-14 21:38 sys_stv
2024-04-13 21:39 sys_stv
2024-04-11 21:40 sys_stv
2024-04-10 21:37 sys_stv
2024-04-09 21:40 sys_stv
2024-04-09 1:13 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='7f45a9$omadc@fmviesa003-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).