From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |FAILURE| pw120522 [PATCH] [v11] mbuf perf test, please ignore
Date: Wed, 7 Dec 2022 02:48:57 -0500 (EST) [thread overview]
Message-ID: <20221207074857.846E145F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 11536 bytes --]
Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/120522
_build patch failure_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Wednesday, December 07 2022 07:35:44
Applied on: CommitID:6c8aed5ab7f6dbed8e71199504fa227f5f60c6fd
Apply patch set 120522 failed:
[1/972] Linking static target drivers/libtmp_rte_net_failsafe.a
[2/972] Linking static target drivers/net/hinic/base/libhinic_base.a
[3/972] Linking static target drivers/net/i40e/base/libi40e_base.a
[4/972] Compiling C object drivers/librte_net_cnxk.so.23.1.p/meson-generated_.._rte_net_cnxk.pmd.c.o
[5/972] Compiling C object drivers/librte_net_cnxk.a.p/meson-generated_.._rte_net_cnxk.pmd.c.o
[6/972] Linking target lib/librte_pipeline.so.23.1
[7/972] Linking target drivers/librte_common_cnxk.so.23.1
[8/972] Linking static target drivers/librte_net_cnxk.a
[9/972] Compiling C object drivers/net/iavf/libiavf_avx512_lib.a.p/iavf_rxtx_vec_avx512.c.o
FAILED: drivers/net/iavf/libiavf_avx512_lib.a.p/iavf_rxtx_vec_avx512.c.o
cc -Idrivers/net/iavf/libiavf_avx512_lib.a.p -Idrivers/net/iavf -I../drivers/net/iavf -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 -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -O3 -include rte_config.h -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-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-strict-aliasing -DCC_AVX2_SUPPORT -DCC_AVX512_SUPPORT -mavx512f -mavx512bw -march=skylake-avx512 -MD -MQ drivers/net/iavf/libiavf_avx512_lib.a.p/iavf_rxtx_vec_avx512.c.o -MF drivers/net/iavf/libiavf_avx512_lib.a.p/iavf_rxtx_vec_avx512.c.o.d -o drivers/net/iavf/libiavf_avx512_lib.a.p/iavf_rxtx_vec_avx512.c.o -c ../drivers/net/iavf/iavf_rxtx_vec_avx512.c
In file included from ../lib/eal/include/dev_driver.h:12:0,
from ../lib/ethdev/ethdev_driver.h:22,
from ../drivers/net/iavf/iavf_rxtx_vec_common.h:8,
from ../drivers/net/iavf/iavf_rxtx_vec_avx512.c:5:
../drivers/net/iavf/iavf_rxtx_vec_common.h: In function ‘iavf_rxq_rearm_common’:
../drivers/net/iavf/iavf_rxtx_vec_common.h:425:46: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
RTE_BUILD_BUG_ON(offsetof(struct rte_mbuf, buf_iova) !=
^
../lib/eal/include/rte_common.h:417:65: note: in definition of macro ‘RTE_BUILD_BUG_ON’
#define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
^~~~~~~~~
In file included from /usr/include/x86_64-linux-gnu/bits/socket.h:27:0,
from /usr/include/x86_64-linux-gnu/sys/socket.h:33,
from ../lib/net/rte_ip.h:23,
from ../lib/ethdev/rte_flow.h:24,
from ../lib/ethdev/rte_eth_ctrl.h:11,
from ../lib/ethdev/rte_ethdev.h:1419,
from ../lib/ethdev/ethdev_driver.h:24,
from ../drivers/net/iavf/iavf_rxtx_vec_common.h:8,
from ../drivers/net/iavf/iavf_rxtx_vec_avx512.c:5:
../drivers/net/iavf/iavf_rxtx_vec_avx512.c: In function ‘iavf_rxq_rearm’:
../drivers/net/iavf/iavf_rxtx_vec_avx512.c:82:26: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
(struct rte_mbuf, buf_iova));
^
../drivers/net/iavf/iavf_rxtx_vec_avx512.c: In function ‘iavf_vtx1’:
../drivers/net/iavf/iavf_rxtx_vec_avx512.c:1900:15: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
pkt->buf_iova + pkt->data_off);
^~~~~~~~
buf_addr
../drivers/net/iavf/iavf_rxtx_vec_avx512.c: In function ‘iavf_vtx’:
../drivers/net/iavf/iavf_rxtx_vec_avx512.c:1950:14: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
pkt[3]->buf_iova + pkt[3]->data_off,
^~~~~~~~
buf_addr
../drivers/net/iavf/iavf_rxtx_vec_avx512.c:1952:14: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
pkt[2]->buf_iova + pkt[2]->data_off,
^~~~~~~~
buf_addr
../drivers/net/iavf/iavf_rxtx_vec_avx512.c:1954:14: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
pkt[1]->buf_iova + pkt[1]->data_off,
^~~~~~~~
buf_addr
../drivers/net/iavf/iavf_rxtx_vec_avx512.c:1956:14: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
pkt[0]->buf_iova + pkt[0]->data_off);
^~~~~~~~
buf_addr
[10/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_metainit.c.o
[11/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_acl.c.o
[12/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_vlan_mode.c.o
[13/972] Compiling C object drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.o
FAILED: drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.o
cc -Idrivers/net/i40e/libi40e_avx512_lib.a.p -Idrivers/net/i40e -I../drivers/net/i40e -Idrivers/net/i40e/base -I../drivers/net/i40e/base -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 -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -O3 -include rte_config.h -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-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DPF_DRIVER -DVF_DRIVER -DINTEGRATED_VF -DX722_A0_SUPPORT -DCC_AVX2_SUPPORT -DCC_AVX512_SUPPORT -mavx512f -mavx512bw -march=skylake-avx512 -MD -MQ drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.o -MF drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.o.d -o drivers/net/i40e/libi40e_avx512_lib.a.p/i40e_rxtx_vec_avx512.c.o -c ../drivers/net/i40e/i40e_rxtx_vec_avx512.c
In file included from ../lib/eal/include/dev_driver.h:12:0,
from ../lib/ethdev/ethdev_driver.h:22,
from ../drivers/net/i40e/i40e_rxtx_vec_avx512.c:6:
../drivers/net/i40e/i40e_rxtx_common_avx.h: In function ‘i40e_rxq_rearm_common’:
../drivers/net/i40e/i40e_rxtx_common_avx.h:61:46: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
RTE_BUILD_BUG_ON(offsetof(struct rte_mbuf, buf_iova) !=
^
../lib/eal/include/rte_common.h:417:65: note: in definition of macro ‘RTE_BUILD_BUG_ON’
#define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
^~~~~~~~~
In file included from /usr/include/x86_64-linux-gnu/bits/socket.h:27:0,
from /usr/include/x86_64-linux-gnu/sys/socket.h:33,
from ../lib/net/rte_ip.h:23,
from ../lib/ethdev/rte_flow.h:24,
from ../lib/ethdev/rte_eth_ctrl.h:11,
from ../lib/ethdev/rte_ethdev.h:1419,
from ../lib/ethdev/ethdev_driver.h:24,
from ../drivers/net/i40e/i40e_rxtx_vec_avx512.c:6:
../drivers/net/i40e/i40e_rxtx_vec_avx512.c: In function ‘i40e_rxq_rearm’:
../drivers/net/i40e/i40e_rxtx_vec_avx512.c:76:30: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
(offsetof(struct rte_mbuf, buf_iova));
^
../drivers/net/i40e/i40e_rxtx_vec_avx512.c: In function ‘vtx1’:
../drivers/net/i40e/i40e_rxtx_vec_avx512.c:997:10: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
pkt->buf_iova + pkt->data_off);
^~~~~~~~
buf_addr
../drivers/net/i40e/i40e_rxtx_vec_avx512.c: In function ‘vtx’:
../drivers/net/i40e/i40e_rxtx_vec_avx512.c:1028:21: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
(hi_qw3, pkt[3]->buf_iova + pkt[3]->data_off,
^~~~~~~~
buf_addr
../drivers/net/i40e/i40e_rxtx_vec_avx512.c:1029:20: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
hi_qw2, pkt[2]->buf_iova + pkt[2]->data_off,
^~~~~~~~
buf_addr
../drivers/net/i40e/i40e_rxtx_vec_avx512.c:1030:20: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
hi_qw1, pkt[1]->buf_iova + pkt[1]->data_off,
^~~~~~~~
buf_addr
../drivers/net/i40e/i40e_rxtx_vec_avx512.c:1031:20: error: ‘struct rte_mbuf’ has no member named ‘buf_iova’; did you mean ‘buf_addr’?
hi_qw0, pkt[0]->buf_iova + pkt[0]->data_off);
^~~~~~~~
buf_addr
[14/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_bst_tcam.c.o
[15/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_ptype_mk.c.o
[16/972] Generating rte_net_failsafe.pmd.c with a custom command
[17/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_pg_cam.c.o
[18/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_mk_grp.c.o
[19/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_parser.c.o
[20/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_imem.c.o
[21/972] Generating symbol file drivers/librte_common_cnxk.so.23.1.p/librte_common_cnxk.so.23.1.symbols
[22/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_dcb.c.o
[23/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_acl_ctrl.c.o
[24/972] Generating rte_net_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[25/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_fdir.c.o
[26/972] Compiling C object drivers/net/ice/base/libice_base.a.p/ice_ptp_hw.c.o
ninja: build stopped: subcommand failed.
https://lab.dpdk.org/results/dashboard/patchsets/24661/
UNH-IOL DPDK Community Lab
next reply other threads:[~2022-12-07 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 7:48 dpdklab [this message]
[not found] <20221207073544.82950-1-mb@smartsharesystems.com>
2022-12-07 8:19 ` |FAILURE| pw120522 [PATCH v11] " 0-day Robot
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=20221207074857.846E145F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).