From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: okaya@kernel.org, robot@bytheb.org
Subject: |FAILURE| pw130327 [PATCH v3 7/7] eal: initialize worker threads once
Date: Tue, 15 Aug 2023 00:19:39 -0400 [thread overview]
Message-ID: <20230815041939.2409343-1-robot@bytheb.org> (raw)
In-Reply-To: <20230815035239.1365591-8-okaya@kernel.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/130327/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/5863440703
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-mini" failed at step Build and test
"ubuntu-20.04-gcc-debug+doc+examples+tests" failed at step Build and test
"ubuntu-20.04-clang-asan+doc+tests" failed at step Build and test
"fedora:37-gcc" failed at step Build
"fedora:37-clang" failed at step Build
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-mini" at step Build and test
####################################################################################
[516/518] Compiling C++ object 'buildtools/chkincs/fe389a9@@chkincs-cpp@exe/meson-generated_rte_fib6.cpp.o'.
[517/518] Compiling C++ object 'buildtools/chkincs/fe389a9@@chkincs-cpp@exe/meson-generated_rte_ipsec_sa.cpp.o'.
[518/518] Linking target buildtools/chkincs/chkincs-cpp.
+ [ -z ]
+ failed=
+ configure_coredump
+ which gdb
+ ulimit -c unlimited
+ sudo sysctl -w kernel.core_pattern=/tmp/dpdk-core.%e.%p
kernel.core_pattern = /tmp/dpdk-core.%e.%p
+ devtools/test-null.sh
EAL: Detected CPU lcores: 2
EAL: Detected NUMA nodes: 1
EAL: Detected shared linkage of DPDK
EAL: failed to parse device "0:0.0"
EAL: Unable to parse device '0:0.0'
EAL: Error - exiting with code: 1
Cause: Cannot init EAL: No such device
devtools/test-null.sh: 29: echo: echo: I/O error
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-mini" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################
[716/718] Compiling C++ object 'buildtools/chkincs/fe389a9@@chkincs-cpp@exe/meson-generated_rte_node_ip6_api.cpp.o'.
[717/718] Compiling C++ object 'buildtools/chkincs/fe389a9@@chkincs-cpp@exe/meson-generated_rte_node_eth_api.cpp.o'.
[718/718] Linking target buildtools/chkincs/chkincs-cpp.
+ [ -z ]
+ failed=
+ configure_coredump
+ which gdb
+ ulimit -c unlimited
+ sudo sysctl -w kernel.core_pattern=/tmp/dpdk-core.%e.%p
kernel.core_pattern = /tmp/dpdk-core.%e.%p
+ devtools/test-null.sh
EAL: Detected CPU lcores: 2
EAL: Detected NUMA nodes: 1
EAL: Detected shared linkage of DPDK
EAL: failed to parse device "net_null1"
EAL: Unable to parse device 'net_null1'
EAL: Error - exiting with code: 1
Cause: Cannot init EAL: No such device
devtools/test-null.sh: 29: echo: echo: I/O error
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-20.04-clang-asan+doc+tests" at step Build and test
####################################################################################
EAL: failed to parse device "net_null1"
EAL: Unable to parse device 'net_null1'
EAL: Error - exiting with code: 1
Cause: Cannot init EAL: No such device
=================================================================
==62588==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4120 byte(s) in 1 object(s) allocated from:
#0 0x4a9ffd in malloc (/home/runner/work/dpdk/dpdk/build/app/dpdk-testpmd+0x4a9ffd)
#1 0x7f0a69c4c061 in eal_plugin_add /home/runner/work/dpdk/dpdk/build/../lib/eal/common/eal_common_options.c:360:10
#2 0x7f0a69c4c061 in eal_parse_common_option /home/runner/work/dpdk/dpdk/build/../lib/eal/common/eal_common_options.c:1750:7
#3 0x7f0a69c949c3 in eal_parse_args /home/runner/work/dpdk/dpdk/build/../lib/eal/linux/eal.c:660:9
#4 0x7f0a69c949c3 in rte_eal_init /home/runner/work/dpdk/dpdk/build/../lib/eal/linux/eal.c:1010:11
#5 0x607164 in main /home/runner/work/dpdk/dpdk/build/../app/test-pmd/testpmd.c:4515:9
#6 0x7f0a612aa082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
SUMMARY: AddressSanitizer: 4120 byte(s) leaked in 1 allocation(s).
devtools/test-null.sh: 29: echo: echo: I/O error
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[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:37-gcc" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:37-gcc" at step Build
####################################################################################
####################################################################################
#### [Begin job log] "fedora:37-clang" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:37-clang" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-08-15 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230815035239.1365591-8-okaya@kernel.org>
2023-08-15 3:51 ` |SUCCESS| pw130321-130327 " qemudev
2023-08-15 3:54 ` |SUCCESS| pw130327 " checkpatch
2023-08-15 3:55 ` |FAILURE| pw130321-130327 " qemudev
2023-08-15 4:19 ` 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=20230815041939.2409343-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=okaya@kernel.org \
--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).