automatic DPDK test reports
 help / color / mirror / Atom feed
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: [dpdk-test-report] |FAILURE| dpdk-next-net-brcm daily Intel builds
Date: 15 Feb 2022 17:40:07 -0800	[thread overview]
Message-ID: <5975f8$eqrr9t@orsmga006-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 7597 bytes --]


Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_


commit 19cd4841fa9f52e59d5f4069d3b3147595f27c70
Author: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date:   Wed Jan 26 10:13:26 2022 -0800

    net/bnxt: fix ring calculation for representors

DPDK git Repo: dpdk-next-net-brcm 


Meson Build Summary: 23 Builds Done, 22 Successful, 1 Failures, 0 Blocked

+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| os           | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| FC35-64      | pass       | pass         |            |            |           |          |            |
| FreeBSD13-64 | pass       | pass         |            | pass       | pass      |          |            |
| RHEL84-64    | pass       | pass         | pass       | pass       | pass      |          |            |
| SUSE15-64    | pass       | pass         |            |            |           |          |            |
| UB2004-32    | pass       |              |            |            |           |          |            |
| UB2004-64    | pass       | pass         | pass       |            |           | pass     | fail       |
| UB2004-64N   | pass       |              |            | pass       |           |          |            |
| UB2110-64    | pass       |              |            |            |           |          |            |
| RHEL85-64    | pass       |              |            |            |           |          |            |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+

Comments: 
Beacasue 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: FC35-64
	Kernel Version: 5.14.16-301.fc35.x86_64
	GCC Version: gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1)
	Clang Version: 13.0.0 (Fedora 13.0.0~rc1-1.fc35)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: FreeBSD13-64
	Kernel Version: 13.0-RELEASE
	GCC Version: gcc (FreeBSD Ports Collection) 10.3.0
	Clang Version: 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc+debug

OS: RHEL84-64
	Kernel Version: 4.18.0-348.7.1.el8_5.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
	Clang Version: 12.0.1 (Red Hat 12.0.1-4.module_el8.5.0+1025+93159d6c)
	ICC Version: 19.1.3.304 (gcc version 8.5.0 compatibility)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug
	x86_64-native-linuxapp-icc

OS: SUSE15-64
	Kernel Version: 5.3.18-57-default
	GCC Version: gcc (SUSE Linux) 7.5.0
	Clang Version: 11.0.1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc

OS: UB2004-32
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
	Clang Version: 10.0.0-4ubuntu1
	i686-native-linuxapp-gcc

OS: UB2004-64
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-doc
	x86_64-native-linuxapp-gcc+16byte

OS: UB2004-64N
	Kernel Version: 5.11.16-051116-generic
	GCC Version: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc+shared

OS: UB2110-64
	Kernel Version: 5.13.0-19-generic
	GCC Version: gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0
	Clang Version: 13.0.0-2
	x86_64-native-linuxapp-gcc

OS: RHEL85-64
	Kernel Version: 4.18.0-348.7.1.el8_5.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
	Clang Version: 12.0.1 (Red Hat 12.0.1-4.module_el8.5.0+1025+93159d6c)
	ICC Version: 19.1.3.304 (gcc version 8.5.0 compatibility)
	x86_64-native-linuxapp-gcc



*Build Failed #1:
OS: UB2004-64
Target: x86_64-native-linuxapp-gcc+16byte
FAILED: drivers/libtmp_rte_net_ice.a.p/net_ice_ice_rxtx.c.o 
gcc -Idrivers/libtmp_rte_net_ice.a.p -Idrivers -I../drivers -Idrivers/net/ice -I../drivers/net/ice -Idrivers/net/ice/base -I../drivers/net/ice/base -Idrivers/common/iavf -I../drivers/common/iavf -Ilib/ethdev -I../lib/ethdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h -Wextra -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -DRTE_LIBRTE_I40E_16BYTE_RX_DESC -DRTE_LIBRTE_ICE_16BYTE_RX_DESC -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DCC_AVX2_SUPPORT -DCC_AVX512_SUPPORT -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.ice -MD -MQ drivers/libtmp_rte_net_ice.a.p/net_ice_ice_rxtx.c.o -MF drivers/libtmp_rte_net_ice.a.p/net_ice_ice_rxtx.c.o.d -o drivers/libtmp_rte_net_ice.a.p/net_ice_ice_rxtx.c.o -c ../drivers/net/ice/ice_rxtx.c
../drivers/net/ice/ice_rxtx.c: In function ‘ice_rxd_to_pkt_fields_by_comms_aux_v1’:
../drivers/net/ice/ice_rxtx.c:128:60: error: unused parameter ‘rxq’ [-Werror=unused-parameter]
  128 | ice_rxd_to_pkt_fields_by_comms_aux_v1(struct ice_rx_queue *rxq,
      |                                       ~~~~~~~~~~~~~~~~~~~~~^~~
../drivers/net/ice/ice_rxtx.c: In function ‘ice_rxd_to_pkt_fields_by_comms_aux_v2’:
../drivers/net/ice/ice_rxtx.c:170:60: error: unused parameter ‘rxq’ [-Werror=unused-parameter]
  170 | ice_rxd_to_pkt_fields_by_comms_aux_v2(struct ice_rx_queue *rxq,
      |                                       ~~~~~~~~~~~~~~~~~~~~~^~~
cc1: all warnings being treated as errors
[1769/3597] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_dcf_sched.c.o
[1770/3597] Compiling C object drivers/libtmp_rte_net_igc.a.p/net_igc_igc_filter.c.o
[1771/3597] Compiling C object drivers/net/igc/base/libigc_base.a.p/igc_phy.c.o
[1772/3597] Compiling C object drivers/libtmp_rte_net_igc.a.p/net_igc_igc_flow.c.o
[1773/3597] Compiling C object drivers/libtmp_rte_net_ionic.a.p/net_ionic_ionic_ethdev.c.o
[1774/3597] Compiling C object drivers/libtmp_rte_net_igc.a.p/net_igc_igc_ethdev.c.o
[1775/3597] Compiling C object drivers/libtmp_rte_net_ionic.a.p/net_ionic_ionic_dev.c.o
[1776/3597] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_rxtx_vec_avx2.c.o
[1777/3597] Compiling C object drivers/libtmp_rte_net_igc.a.p/net_igc_igc_txrx.c.o
ninja: build stopped


DPDK STV team

             reply	other threads:[~2022-02-16  1:40 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  1:40 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-21 22:40 sys_stv
2023-05-20 22:40 sys_stv
2023-05-19 22:54 sys_stv
2023-05-18 23:06 sys_stv
2023-05-17 23:37 sys_stv
2023-05-16 22:58 sys_stv
2023-05-15 22:42 sys_stv
2023-01-09 22:23 sys_stv
2023-01-09  2:50 sys_stv
2023-01-08 22:24 sys_stv
2023-01-07 22:24 sys_stv
2023-01-06 22:25 sys_stv
2023-01-05 22:23 sys_stv
2022-11-30 22:29 sys_stv
2022-11-28 22:29 sys_stv
2022-11-28  9:53 sys_stv
2022-11-23 22:29 sys_stv
2022-11-23  6:56 sys_stv
2022-10-20 22:42 sys_stv
2022-10-13 22:11 sys_stv
2022-09-16  6:35 sys_stv
2022-09-16  2:57 sys_stv
2022-09-15 21:56 sys_stv
2022-09-14 21:55 sys_stv
2022-09-12 21:55 sys_stv
2022-09-07 13:16 sys_stv
2022-06-25 21:50 sys_stv
2022-06-24 21:51 sys_stv
2022-06-07 21:49 sys_stv
2022-06-06 21:49 sys_stv
2022-06-01 22:43 sys_stv
2022-06-01 21:49 sys_stv
2022-06-01  4:42 sys_stv
2022-06-01  2:39 sys_stv
2022-05-31 22:42 sys_stv
2022-05-31 21:49 sys_stv
2022-05-31 16:42 sys_stv
2022-05-31 10:42 sys_stv
2022-05-31  4:42 sys_stv
2022-05-30 21:49 sys_stv
2022-05-18 22:45 sys_stv
2022-05-18 21:51 sys_stv
2022-05-17 22:46 sys_stv
2022-05-17 21:51 sys_stv
2022-05-17 16:43 sys_stv
2022-05-17 11:17 sys_stv
2022-05-17 10:21 sys_stv
2022-05-17  8:29 sys_stv
2022-05-16 22:58 sys_stv
2022-05-16 22:01 sys_stv
2022-05-07  4:43 sys_stv
2022-05-06 22:58 sys_stv
2022-05-06 21:56 sys_stv
2022-03-18 22:05 sys_stv
2022-02-17 16:43 sys_stv
2022-02-17 10:43 sys_stv
2022-02-17  4:43 sys_stv
2022-02-16 22:43 sys_stv
2022-02-16 10:43 sys_stv
2022-02-16  4:43 sys_stv
2022-02-15 16:43 sys_stv
2022-02-15  7:13 sys_stv
2022-01-28 10:42 sys_stv
2022-01-28  9:20 sys_stv
2022-01-28  4:42 sys_stv
2022-01-27 22:42 sys_stv
2022-01-27 16:42 sys_stv
2022-01-27 10:42 sys_stv
2022-01-27  7:53 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='5975f8$eqrr9t@orsmga006-auth.jf.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).