From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: beilei.xing@intel.com, robot@bytheb.org
Subject: |FAILURE| pw126446 [PATCH v3] net/idpf: add VF support
Date: Mon, 24 Apr 2023 05:39:39 -0400 [thread overview]
Message-ID: <20230424093939.1022779-1-robot@bytheb.org> (raw)
In-Reply-To: <20230424082852.14206-1-beilei.xing@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/126446/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4784427123
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-clang-asan+doc+tests" failed at step Build and test
"fedora:35-clang" failed at step Build
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-clang-asan+doc+tests" at step Build and test
####################################################################################
[558/4342] Linking target drivers/librte_common_iavf.so.23.2.
[559/4342] Compiling C object 'drivers/common/idpf/281975e@@idpf_common_avx512_lib@sta/idpf_common_rxtx_avx512.c.o'.
[560/4342] Linking static target drivers/common/idpf/libidpf_common_avx512_lib.a.
[561/4342] Generating symbol file 'drivers/a715181@@rte_common_iavf@sha/librte_common_iavf.so.23.2.symbols'.
[562/4342] Compiling C object 'drivers/a715181@@tmp_rte_common_idpf@sta/common_idpf_idpf_common_device.c.o'.
FAILED: drivers/a715181@@tmp_rte_common_idpf@sta/common_idpf_idpf_common_device.c.o
ccache clang -Idrivers/a715181@@tmp_rte_common_idpf@sta -Idrivers -I../drivers -Idrivers/common/idpf -I../drivers/common/idpf -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/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Xclang -fcolor-diagnostics -fsanitize=address -fno-omit-frame-pointer -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O2 -g -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-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=corei7 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DCC_AVX512_SUPPORT -Wno-unused-value -Wno-unused-variable -Wno-unused-parameter -Wno-implicit-fallthrough -Wno-strict-aliasing -DRTE_LOG_DEFAULT_LOGTYPE=pmd.common.idpf -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ 'drivers/a715181@@tmp_rte_common_idpf@sta/common_idpf_idpf_common_device.c.o' -MF 'drivers/a715181@@tmp_rte_common_idpf@sta/common_idpf_idpf_common_device.c.o.d' -o 'drivers/a715181@@tmp_rte_common_idpf@sta/common_idpf_idpf_common_device.c.o' -c ../drivers/common/idpf/idpf_common_device.c
../drivers/common/idpf/idpf_common_device.c:376:13: error: variable 'ret' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized]
} else if (hw->device_id == IDPF_DEV_ID_SRIOV) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/common/idpf/idpf_common_device.c:379:6: note: uninitialized use occurs here
if (ret != 0) {
^~~
../drivers/common/idpf/idpf_common_device.c:376:9: note: remove the 'if' if its condition is always true
} else if (hw->device_id == IDPF_DEV_ID_SRIOV) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/common/idpf/idpf_common_device.c:371:9: note: initialize the variable 'ret' to silence this warning
int ret;
^
= 0
1 error generated.
[563/4342] Compiling C object 'drivers/a715181@@tmp_rte_common_idpf@sta/common_idpf_idpf_common_rxtx.c.o'.
[564/4342] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_table_action.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-clang-asan+doc+tests" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "fedora:35-clang" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:35-clang" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-04-24 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230424082852.14206-1-beilei.xing@intel.com>
2023-04-24 8:42 ` |SUCCESS| " qemudev
2023-04-24 8:46 ` qemudev
2023-04-24 8:52 ` checkpatch
2023-04-24 9:39 ` 0-day Robot [this message]
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=20230424093939.1022779-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=beilei.xing@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).