From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: wang.junlong1@zte.com.cn, robot@bytheb.org
Subject: |FAILURE| pw145956 [PATCH v5 9/9] net/zxdh: add zxdh dev configure ops
Date: Tue, 15 Oct 2024 02:42:58 -0400 [thread overview]
Message-ID: <20241015064258.2382501-1-robot@bytheb.org> (raw)
In-Reply-To: <20241015054435.1751245-8-wang.junlong1@zte.com.cn>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/145956/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11340220834
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-stdatomic" failed at step Build and test
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
"fedora:39-gcc" failed at step Build
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-stdatomic" at step Build and test
####################################################################################
951 | struct bar_msg_header msg_header;
| ^~~~~~~~~~
../drivers/net/zxdh/zxdh_msg.c:976:60: error: ‘msg_header.sync’ may be used uninitialized [-Werror=maybe-uninitialized]
976 | uint64_t reps_addr = zxdh_reply_addr_get(msg_header.sync, src, dst, virt_addr);
| ~~~~~~~~~~^~~~~
../drivers/net/zxdh/zxdh_msg.c:951:31: note: ‘msg_header’ declared here
951 | struct bar_msg_header msg_header;
| ^~~~~~~~~~
In function ‘zxdh_bar_msg_ack_async_msg_proc’,
inlined from ‘zxdh_bar_irq_recv’ at ../drivers/net/zxdh/zxdh_msg.c:984:3:
../drivers/net/zxdh/zxdh_msg.c:860:78: error: ‘msg_header.msg_id’ may be used uninitialized [-Werror=maybe-uninitialized]
860 | struct seqid_item *reps_info = &g_seqid_ring.reps_info_tbl[msg_header->msg_id];
| ~~~~~~~~~~^~~~~~~~
../drivers/net/zxdh/zxdh_msg.c: In function ‘zxdh_bar_irq_recv’:
../drivers/net/zxdh/zxdh_msg.c:951:31: note: ‘msg_header’ declared here
951 | struct bar_msg_header msg_header;
| ^~~~~~~~~~
cc1: all warnings being treated as errors
[2198/3046] Compiling C object 'drivers/a715181@@tmp_rte_net_zxdh@sta/net_zxdh_zxdh_queue.c.o'.
[2199/3046] Compiling C object 'drivers/a715181@@tmp_rte_raw_cnxk_bphy@sta/raw_cnxk_bphy_cnxk_bphy_cgx.c.o'.
[2200/3046] Generating rte_net_vmxnet3.pmd.c with a custom command.
[2201/3046] Compiling C object 'drivers/a715181@@tmp_rte_raw_cnxk_bphy@sta/raw_cnxk_bphy_cnxk_bphy.c.o'.
[2202/3046] Compiling C object 'drivers/a715181@@tmp_rte_net_zxdh@sta/net_zxdh_zxdh_common.c.o'.
ninja: build stopped: subcommand failed.
##[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-asan+doc+tests" at step Build and test
####################################################################################
91/100 DPDK:fast-tests / telemetry_json_autotest OK 0.37 s
92/100 DPDK:fast-tests / thash_autotest OK 0.37 s
93/100 DPDK:fast-tests / threads_autotest OK 0.52 s
94/100 DPDK:fast-tests / ticketlock_autotest OK 0.42 s
95/100 DPDK:fast-tests / timer_autotest OK 2.87 s
96/100 DPDK:fast-tests / trace_autotest OK 0.37 s
97/100 DPDK:fast-tests / trace_autotest_with_traces OK 0.37 s
98/100 DPDK:fast-tests / vdev_autotest OK 0.37 s
99/100 DPDK:fast-tests / version_autotest OK 0.37 s
100/100 DPDK:fast-tests / telemetry_all OK 1.12 s
Ok: 93
Expected Fail: 0
Fail: 1
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-clang-asan+doc+tests" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "fedora:39-gcc" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-gcc" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-10-15 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241015054435.1751245-8-wang.junlong1@zte.com.cn>
2024-10-15 5:30 ` |SUCCESS| pw145952-145956 " qemudev
2024-10-15 5:35 ` qemudev
2024-10-15 5:51 ` |WARNING| pw145956 " checkpatch
2024-10-15 6:42 ` 0-day Robot [this message]
2024-10-15 8:23 ` |SUCCESS| pw145952-145956 [PATCH] [v5,9/9] net/zxdh: add zxdh dev co 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=20241015064258.2382501-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
--cc=wang.junlong1@zte.com.cn \
/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).