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-net-intel| 3b017bdc4c| Intel-compilation
Date: 12 Aug 2024 16:13:12 -0700 [thread overview]
Message-ID: <453681$1ruc2f@fmviesa005-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5184 bytes --]
Test-Label: Intel-compilation
Test-Status: SUCCESS
_Compilation OK_
commit 3b017bdc4c25e2cd6733a9363e9c566b95834cc4
Author: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tue Jul 23 14:10:56 2024 +0100
net/ice: fix E830 PTP PHY model
DPDK git Repo: dpdk-next-net-intel
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.8-64 | pass | | | | | | |
| FreeBSD14-64 | pass | pass | | pass | pass | | |
| RHEL94-64 | pass | pass | | pass | pass | | |
| SUSE15-64 | pass | pass | | | | | |
| CBL-Mariner2.0-64 | pass | | | | | | |
| UB2404-32 | pass | | | | | | |
| RHEL93-64 | pass | | | | | | |
| UB2404-64N | pass | | | pass | | | |
| UB2404-64 | pass | pass | | | | pass | pass |
| RHEL94-64Rt | pass | | | | | | |
| UB2204-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.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: 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: 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: UB2404-32
Kernel Version: 6.8.0-31-generic
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: NA
i686-native-linuxapp-gcc
OS: RHEL93-64
Kernel Version: 5.14.0-362.8.1.el9_3.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
OS: UB2404-64N
Kernel Version: 6.9.1-060901-generic
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: 18.1.3 (1)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc+shared
OS: UB2404-64
Kernel Version: 6.8.0-31-generic
GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang Version: 18.1.3 (1)
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: UB2204-64
Kernel Version: 5.15.0-94-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
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: 18.1.3 (1)
x86_64-native-linuxapp-gcc
DPDK STV team
next reply other threads:[~2024-08-12 23:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 23:13 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-21 23:16 sys_stv
2024-08-20 22:57 sys_stv
2024-08-19 22:47 sys_stv
2024-08-18 22:48 sys_stv
2024-08-17 22:47 sys_stv
2024-08-16 22:56 sys_stv
2024-08-15 22:47 sys_stv
2024-08-14 22:48 sys_stv
2024-08-13 22:56 sys_stv
2024-08-11 22:46 sys_stv
2024-08-10 22:48 sys_stv
2024-08-09 22:46 sys_stv
2024-08-07 22:43 sys_stv
2024-08-06 22:32 sys_stv
2024-08-05 22:42 sys_stv
2024-08-04 22:34 sys_stv
2024-08-03 22:34 sys_stv
2024-08-02 22:33 sys_stv
2024-08-01 22:32 sys_stv
2024-07-31 23:03 sys_stv
2024-07-30 22:33 sys_stv
2024-07-29 22:38 sys_stv
2024-07-28 22:33 sys_stv
2024-07-27 22:31 sys_stv
2024-07-26 22:42 sys_stv
2024-07-24 22:42 sys_stv
2024-07-23 22:56 sys_stv
2024-07-23 15:18 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='453681$1ruc2f@fmviesa005-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).