automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: mb@smartsharesystems.com, robot@bytheb.org
Subject: |FAILURE| pw147124 [PATCH v4] ethdev: TEST support single queue per port
Date: Thu, 24 Oct 2024 11:47:15 -0400	[thread overview]
Message-ID: <20241024154715.1021798-1-robot@bytheb.org> (raw)
In-Reply-To: <20241024145550.985298-1-mb@smartsharesystems.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/147124/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11502190506
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-clang-stdatomic" failed at step Build and test
"ubuntu-22.04-gcc-debug+doc+examples+tests" failed at step Build and test
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
"fedora:39-clang" failed at step Build
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
[1165/3072] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_bnx2x_vfpf.c.o
[1166/3072] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_bnx2x_stats.c.o
[1167/3072] Compiling C object drivers/net/bnxt/libbnxt_avx2_lib.a.p/bnxt_rxtx_vec_avx2.c.o
[1168/3072] Linking static target drivers/net/bnxt/libbnxt_avx2_lib.a
[1169/3072] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_ecore_sp.c.o
[1170/3072] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o
FAILED: drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o 
ccache clang -Idrivers/libtmp_rte_net_bnxt.a.p -Idrivers -I../drivers -Idrivers/net/bnxt -I../drivers/net/bnxt -Idrivers/net/bnxt/tf_ulp -I../drivers/net/bnxt/tf_ulp -Idrivers/net/bnxt/tf_ulp/generic_templates -I../drivers/net/bnxt/tf_ulp/generic_templates -Idrivers/net/bnxt/tf_core -I../drivers/net/bnxt/tf_core -Idrivers/net/bnxt/hcapi/cfa -I../drivers/net/bnxt/hcapi/cfa -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/log -I../lib/log -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 -Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -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 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DSUPPORT_CFA_HW_ALL=1 -DBNXT_TF_APP_ID=0 -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.bnxt -MD -MQ drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o -MF drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o.d -o drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o -c ../drivers/net/bnxt/bnxt_ethdev.c
../drivers/net/bnxt/bnxt_ethdev.c:845:13: error: unknown pragma ignored [-Werror,-Wunknown-pragmas]
#pragma GCC push_options
            ^
../drivers/net/bnxt/bnxt_ethdev.c:846:13: error: unknown pragma ignored [-Werror,-Wunknown-pragmas]
#pragma GCC optimize("no-peel-loops")
            ^
../drivers/net/bnxt/bnxt_ethdev.c:1011:13: error: unknown pragma ignored [-Werror,-Wunknown-pragmas]
#pragma GCC pop_options
            ^
3 errors generated.
[1171/3072] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_stats.c.o
[1172/3072] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_rxr.c.o
[1173/3072] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_elink.c.o
[1174/3072] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_bnx2x.c.o
[1175/3072] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_hwrm.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################
108/116 DPDK:fast-tests / thash_autotest                 OK              0.25s
109/116 DPDK:fast-tests / threads_autotest               OK              0.35s
110/116 DPDK:fast-tests / ticketlock_autotest            OK              0.27s
111/116 DPDK:fast-tests / timer_autotest                 OK              2.81s
112/116 DPDK:fast-tests / trace_autotest                 OK              0.24s
113/116 DPDK:fast-tests / trace_autotest_with_traces     OK              0.24s
114/116 DPDK:fast-tests / vdev_autotest                  OK              0.23s
115/116 DPDK:fast-tests / version_autotest               OK              0.23s
116/116 DPDK:fast-tests / telemetry_all                  OK              1.06s


Ok:                 108 
Expected Fail:      0   
Fail:               2   
Unexpected Pass:    0   
Skipped:            6   
Timeout:            0   

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
[1176/6449] Linking target drivers/librte_net_avp.so.25.0
[1177/6449] Linking static target drivers/librte_net_avp.a
[1178/6449] Linking static target drivers/net/bnxt/libbnxt_avx2_lib.a
[1179/6449] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_stats.c.o
[1180/6449] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_irq.c.o
[1181/6449] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o
FAILED: drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o 
ccache clang -Idrivers/libtmp_rte_net_bnxt.a.p -Idrivers -I../drivers -Idrivers/net/bnxt -I../drivers/net/bnxt -Idrivers/net/bnxt/tf_ulp -I../drivers/net/bnxt/tf_ulp -Idrivers/net/bnxt/tf_ulp/generic_templates -I../drivers/net/bnxt/tf_ulp/generic_templates -Idrivers/net/bnxt/tf_core -I../drivers/net/bnxt/tf_core -Idrivers/net/bnxt/hcapi/cfa -I../drivers/net/bnxt/hcapi/cfa -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/log -I../lib/log -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 -Xclang -fcolor-diagnostics -fsanitize=address -fno-omit-frame-pointer -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -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 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DSUPPORT_CFA_HW_ALL=1 -DBNXT_TF_APP_ID=0 -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.bnxt -MD -MQ drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o -MF drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o.d -o drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o -c ../drivers/net/bnxt/bnxt_ethdev.c
../drivers/net/bnxt/bnxt_ethdev.c:845:13: error: unknown pragma ignored [-Werror,-Wunknown-pragmas]
#pragma GCC push_options
            ^
../drivers/net/bnxt/bnxt_ethdev.c:846:13: error: unknown pragma ignored [-Werror,-Wunknown-pragmas]
#pragma GCC optimize("no-peel-loops")
            ^
../drivers/net/bnxt/bnxt_ethdev.c:1011:13: error: unknown pragma ignored [-Werror,-Wunknown-pragmas]
#pragma GCC pop_options
            ^
3 errors generated.
[1182/6449] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_cpr.c.o
[1183/6449] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_bnx2x.c.o
[1184/6449] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_rxr.c.o
[1185/6449] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_elink.c.o
[1186/6449] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "fedora:39-clang" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-clang" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-10-24 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241024145550.985298-1-mb@smartsharesystems.com>
2024-10-24 14:29 ` |SUCCESS| " qemudev
2024-10-24 14:33 ` |FAILURE| " qemudev
2024-10-24 14:56 ` |WARNING| " checkpatch
2024-10-24 15:47 ` 0-day Robot [this message]
2024-10-24 17:52 ` |SUCCESS| pw147124 [PATCH] [v4] ethdev: TEST support single queue pe dpdklab
2024-10-24 19:09 ` dpdklab
2024-10-24 19:14 ` |FAILURE| " dpdklab
2024-10-24 19:18 ` dpdklab

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=20241024154715.1021798-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=mb@smartsharesystems.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).