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 daily Intel builds
Date: 20 Jan 2022 23:55:46 -0800	[thread overview]
Message-ID: <b0e710$emsc3f@orsmga002-auth.jf.intel.com> (raw)

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


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


commit 9cc217a28310d21fba56e5eceb740b4feb7e0949
Author: Ruifeng Wang <ruifeng.wang@arm.com>
Date:   Thu Jan 20 10:38:00 2022 +0800

    config: add arch define for Arm

DPDK git Repo: dpdk 


Meson Build Summary: 22 Builds Done, 21 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      |          |            |
| RHEL85-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       |              |            |            |           |          |            |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
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: 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)
	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



*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
[1632/3050] Compiling C object drivers/net/igc/base/libigc_base.a.p/igc_manage.c.o
[1633/3050] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_dcf_ethdev.c.o
[1634/3050] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_dcf_parent.c.o
[1635/3050] Compiling C object drivers/net/igc/base/libigc_base.a.p/igc_nvm.c.o
[1636/3050] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_rxtx_vec_sse.c.o
[1637/3050] Compiling C object drivers/net/igc/base/libigc_base.a.p/igc_i225.c.o
[1638/3050] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_dcf_sched.c.o
[1639/3050] Compiling C object drivers/net/ice/libice_avx512_lib.a.p/ice_rxtx_vec_avx512.c.o
[1640/3050] Compiling C object drivers/libtmp_rte_net_ice.a.p/net_ice_ice_rxtx_vec_avx2.c.o
ninja: build stopped


DPDK STV team

             reply	other threads:[~2022-01-21  7:55 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21  7:55 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-19 21:15 sys_stv
2023-02-07  8:15 sys_stv
2023-02-07  5:05 sys_stv
2023-01-09  5:34 sys_stv
2022-12-08 21:31 sys_stv
2022-12-06 13:02 sys_stv
2022-12-05  3:36 sys_stv
2022-10-31  5:48 sys_stv
2022-10-11 10:06 sys_stv
2022-09-29  7:48 sys_stv
2022-09-29  5:44 sys_stv
2022-09-29  3:30 sys_stv
2022-09-21 21:06 sys_stv
2022-09-20  9:05 sys_stv
2022-09-19  5:24 sys_stv
2022-09-19  2:38 sys_stv
2022-09-16 10:09 sys_stv
2022-09-15 17:01 sys_stv
2022-09-14 21:06 sys_stv
2022-09-07  8:19 sys_stv
2022-08-30  7:51 sys_stv
2022-08-24  6:11 sys_stv
2022-06-22 21:09 sys_stv
2022-06-09  9:08 sys_stv
2022-06-06  7:26 sys_stv
2022-06-06  2:06 sys_stv
2022-06-01 21:06 sys_stv
2022-06-01  1:57 sys_stv
2022-05-31 21:06 sys_stv
2022-05-30  8:26 sys_stv
2022-05-26  8:57 sys_stv
2022-05-20  5:13 sys_stv
2022-05-20  4:47 sys_stv
2022-05-18 21:07 sys_stv
2022-05-18 10:08 sys_stv
2022-05-17 21:07 sys_stv
2022-05-17  9:36 sys_stv
2022-05-17  9:15 sys_stv
2022-05-17  8:58 sys_stv
2022-05-16 21:06 sys_stv
2022-05-07  7:26 sys_stv
2022-05-06 21:06 sys_stv
2022-05-06  9:49 sys_stv
2022-05-06  9:32 sys_stv
2022-03-08 21:07 sys_stv
2022-03-08 17:16 sys_stv
2022-01-21  7:59 sys_stv
2021-12-18 21:50 sys_stv
2021-10-22 22:14 sys_stv
2021-10-14  3:03 sys_stv
2021-08-15 22:10 sys_stv
2021-06-29 15:39 sys_stv
2021-05-27 22:08 sys_stv
2021-05-07  1:05 sys_stv
2021-03-22 22:07 sys_stv
2021-01-28 22:07 sys_stv
2021-01-27 22:07 sys_stv
2021-01-26 22:08 sys_stv
2021-01-26  6:13 sys_stv
2020-11-05 22:08 sys_stv
2020-11-03 22:07 sys_stv
2020-10-20  5:41 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='b0e710$emsc3f@orsmga002-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).