automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: shperetz@nvidia.com, robot@bytheb.org
Subject: |FAILURE| pw150593 [PATCH v4] bus: fix inconsistent representation of PCI numbers
Date: Wed, 29 Jan 2025 05:05:19 -0500	[thread overview]
Message-ID: <20250129100519.1512932-1-robot@bytheb.org> (raw)
In-Reply-To: <20250129085416.226718-1-shperetz@nvidia.com>

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-mini" at step Build and test
####################################################################################
[2104/2106] Compiling C++ object buildtools/chkincs/chkincs-cpp-all.p/meson-generated_rte_thash.cpp.o
[2105/2106] Compiling C++ object buildtools/chkincs/chkincs-cpp-all.p/meson-generated_rte_stack.cpp.o
[2106/2106] Linking target buildtools/chkincs/chkincs-cpp-all
+ [ -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: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: failed to parse device "net_null1"
EAL: Unable to parse device 'net_null1'
EAL: Error - exiting with code: 1
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-22.04-gcc-mini" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-stdatomic" at step Build and test
####################################################################################
[3214/3216] Linking target examples/dpdk-l3fwd
[3215/3216] Compiling C object app/dpdk-test.p/test_test_memcpy_perf.c.o
[3216/3216] Linking target app/dpdk-test
+ [ -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: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: failed to parse device "net_null1"
EAL: Unable to parse device 'net_null1'
EAL: Error - exiting with code: 1
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-22.04-gcc-stdatomic" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
[3214/3216] Linking target examples/dpdk-l2fwd
[3215/3216] Linking target examples/dpdk-l3fwd
[3216/3216] Linking target app/dpdk-test
+ [ -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: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: failed to parse device "net_null1"
EAL: Unable to parse device 'net_null1'
EAL: Error - exiting with code: 1
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-22.04-clang-stdatomic" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
[6650/6652] Compiling C++ object buildtools/chkincs/chkincs-cpp-all.p/meson-generated_bus_ifpga_driver.cpp.o
[6651/6652] Compiling C++ object buildtools/chkincs/chkincs-cpp-all.p/meson-generated_cnxk_dma_event_dp.cpp.o
[6652/6652] Linking target buildtools/chkincs/chkincs-cpp-all
+ [ -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: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: failed to parse device "net_null1"
EAL: Unable to parse device 'net_null1'
EAL: Error - exiting with code: 1
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-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
[6650/6652] Compiling C++ object buildtools/chkincs/chkincs-cpp-all.p/meson-generated_bus_ifpga_driver.cpp.o
[6651/6652] Compiling C++ object buildtools/chkincs/chkincs-cpp-all.p/meson-generated_cnxk_dma_event_dp.cpp.o
[6652/6652] Linking target buildtools/chkincs/chkincs-cpp-all
+ [ -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: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: failed to parse device "net_null1"
EAL: Unable to parse device 'net_null1'
EAL: Error - exiting with code: 1
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-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-static-i386" at step Build and test
####################################################################################
[5601/5603] Compiling C++ object buildtools/chkincs/chkincs-cpp-all.p/meson-generated_rte_node_ip6_api.cpp.o
[5602/5603] Compiling C++ object buildtools/chkincs/chkincs-cpp-all.p/meson-generated_bus_ifpga_driver.cpp.o
[5603/5603] Linking target buildtools/chkincs/chkincs-cpp-all
+ [ -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: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: failed to parse device "net_null1"
EAL: Unable to parse device 'net_null1'
EAL: Error - exiting with code: 1
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-22.04-gcc-static-i386" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "fedora:39-gcc" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-gcc" at step Build
####################################################################################




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

  parent reply	other threads:[~2025-01-29 10:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250129085416.226718-1-shperetz@nvidia.com>
2025-01-29  8:21 ` |SUCCESS| " qemudev
2025-01-29  8:25 ` |FAILURE| " qemudev
2025-01-29  8:55 ` |WARNING| " checkpatch
2025-01-29 10:01 ` |SUCCESS| pw150593 [PATCH] [v4] bus: fix inconsistent representation dpdklab
2025-01-29 10:05 ` 0-day Robot [this message]
2025-01-29 10:06 ` dpdklab
2025-01-29 10:11 ` |FAILURE| " dpdklab
2025-01-29 10:13 ` dpdklab
2025-01-29 10:15 ` |SUCCESS| " dpdklab
2025-01-29 10:19 ` |WARNING| " dpdklab
2025-01-29 10:24 ` |FAILURE| " dpdklab
2025-01-29 10:29 ` |PENDING| " dpdklab
2025-01-29 10:38 ` |WARNING| " dpdklab
2025-01-29 10:47 ` |PENDING| " dpdklab
2025-01-29 10:50 ` |WARNING| " dpdklab
2025-01-29 10:57 ` |PENDING| " dpdklab
2025-01-29 11:14 ` |FAILURE| " dpdklab
2025-01-29 11:46 ` |SUCCESS| " dpdklab
2025-01-29 12:58 ` |WARNING| " dpdklab
2025-01-29 13:28 ` dpdklab
2025-01-29 15:22 ` |FAILURE| " dpdklab
2025-01-29 17:43 ` |SUCCESS| " dpdklab
2025-01-30  2:26 ` |FAILURE| " 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=20250129100519.1512932-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=shperetz@nvidia.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).