automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(92311) [5/5] net/hns3: select Tx prepare based on Tx offload
Date: 28 Apr 2021 00:56:33 -0700	[thread overview]
Message-ID: <613e7c$cq84h3@orsmga008-auth.jf.intel.com> (raw)

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


Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/92311

_Compilation issues_

Submitter: Min Hu (Connor) <humin29@huawei.com>
Date: 2021-04-28 07:20:55
Reply_mail: 1619594455-56787-6-git-send-email-humin29@huawei.com

DPDK git baseline: Repo:dpdk-next-net, CommitID: 8b1e6d9eb25cbd86a0ad9b990eaf598dc9f5a15a


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

+------------------+------------+--------------+------------+------------+-----------+----------+
| os               | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document |
+------------------+------------+--------------+------------+------------+-----------+----------+
| UB2004-64        | pass       | pass         | pass       |            |           | pass     |
| RHEL83-64        | pass       |              |            |            |           |          |
| FC33-64          | pass       | pass         |            |            |           |          |
| CentOsStream8-64 | pass       |              |            |            |           |          |
| UB2104-64        | pass       |              |            |            |           |          |
| WIN10-64         |            | pass         |            |            |           |          |
| UB2004-32        | pass       |              |            |            |           |          |
| CENTOS83-64      | pass       | pass         | pass       | pass       | FAIL      |          |
| FreeBSD1201-64   | pass       | pass         |            | pass       | pass      |          |
| SUSE15-64        | pass       | pass         |            |            |           |          |
+------------------+------------+--------------+------------+------------+-----------+----------+
Test environment and configuration as below:


OS: UB2004-64
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.2.0-5ubuntu1~20.04) 10.2.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

OS: RHEL83-64
	Kernel Version: 4.18.0-240.el8.x86_64
	GCC Version: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
	Clang Version: 10.0.1 (Red Hat 10.0.1-1.module+el8.3.0+7459+90c24896)
	x86_64-native-linuxapp-gcc

OS: FC33-64
	Kernel Version: 5.8.16-300.fc33.x86_64
	GCC Version: gcc (GCC) 10.2.1 20201005 (Red Hat 10.2.1-5)
	Clang Version: 11.0.0 (Fedora 11.0.0-1.fc33)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: CentOsStream8-64
	Kernel Version: 4.18.0-257.el8.x86_64
	GCC Version: gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
	Clang Version: 11.0.0 (Red Hat 11.0.0-0.2.rc2.module_el8.4.0+533+50191577)
	x86_64-native-linuxapp-gcc

OS: UB2104-64
	Kernel Version: 5.11.0-16-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0
	Clang Version: 12.0.0-1ubuntu1
	x86_64-native-linuxapp-gcc

OS: WIN10-64
	Kernel Version: N/A
	GCC Version: N/A
	Clang Version: Clang 8.0.0
	x86_64-windows-clang

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

OS: CENTOS83-64
	Kernel Version: 4.18.0-240.1.1.el8_3.x86_64
	GCC Version: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
	Clang Version: 10.0.1 (Red Hat 10.0.1-1.module_el8.3.0+467+cb298d5b)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-icc
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug

OS: FreeBSD1201-64
	Kernel Version: 12.1-RELEASE
	GCC Version: gcc (FreeBSD Ports Collection) 9.2.0
	Clang Version: 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc+debug

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



*Build Failed #1:
OS: CENTOS83-64
Target: x86_64-native-linuxapp-gcc+debug
FAILED: drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_rxtx.c.o 
gcc -Idrivers/libtmp_rte_net_hns3.a.p -Idrivers -I../drivers -Idrivers/net/hns3 -I../drivers/net/hns3 -Ilib/librte_ethdev -I../lib/librte_ethdev -I. -I.. -Iconfig -I../config -Ilib/librte_eal/include -I../lib/librte_eal/include -Ilib/librte_eal/linux/include -I../lib/librte_eal/linux/include -Ilib/librte_eal/x86/include -I../lib/librte_eal/x86/include -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_metrics -I../lib/librte_metrics -Ilib/librte_telemetry -I../lib/librte_telemetry -Ilib/librte_net -I../lib/librte_net -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_meter -I../lib/librte_meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/librte_pci -I../lib/librte_pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/librte_hash -I../lib/librte_hash -Ilib/librte_rcu -I../lib/librte_rcu -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O2 -g -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-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -MD -MQ drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_rxtx.c.o -MF drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_rxtx.c.o.d -o drivers/libtmp_rte_net_hns3.a.p/net_hns3_hns3_rxtx.c.o -c ../drivers/net/hns3/hns3_rxtx.c
../drivers/net/hns3/hns3_rxtx.c: In function ‘hns3_get_tx_prep_needed’:
../drivers/net/hns3/hns3_rxtx.c:4212:45: error: unused parameter ‘dev’ [-Werror=unused-parameter]
 hns3_get_tx_prep_needed(struct rte_eth_dev *dev)
                         ~~~~~~~~~~~~~~~~~~~~^~~
cc1: all warnings being treated as errors
[1310/2730] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_rxtx_vec_avx2.c.o
[1311/2730] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_rxtx_vec_sse.c.o
[1312/2730] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_common.c.o
[1313/2730] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_dcb.c.o
[1314/2730] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_sched.c.o
[1315/2730] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_switch.c.o
[1316/2730] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_flow.c.o
[1317/2730] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_flex_pipe.c.o
[1318/2730] Compiling C object drivers/net/iavf/libiavf_avx512_lib.a.p/iavf_rxtx_vec_avx512.c.o
ninja: build stopped


DPDK STV team

                 reply	other threads:[~2021-04-28  7:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='613e7c$cq84h3@orsmga008-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    /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).