From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: zhoumin@loongson.cn, robot@bytheb.org
Subject: |FAILURE| pw115554 [PATCH v6 7/7] ci: add LOONGARCH64 cross compilation job
Date: Sat, 27 Aug 2022 06:20:01 -0400 [thread overview]
Message-ID: <20220827102001.16566-1-robot@bytheb.org> (raw)
In-Reply-To: <20220827085908.52080-8-zhoumin@loongson.cn>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/115554/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/2938743131
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-shared-loongarch64" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-shared-loongarch64" at step Build and test
####################################################################################
inlined from ‘virtio_dev_rx_async_packed’ at ../lib/vhost/virtio_net.c:1840:6,
inlined from ‘virtio_dev_rx_async_submit_packed.constprop’ at ../lib/vhost/virtio_net.c:1900:7:
../lib/vhost/virtio_net.c:1160:18: error: ‘buf_vec[0].buf_iova’ may be used uninitialized [-Werror=maybe-uninitialized]
1160 | buf_iova = buf_vec[vec_idx].buf_iova;
| ~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/vhost/virtio_net.c: In function ‘virtio_dev_rx_async_submit_packed.constprop’:
../lib/vhost/virtio_net.c:1838:27: note: ‘buf_vec’ declared here
1838 | struct buf_vector buf_vec[BUF_VECTOR_MAX];
| ^~~~~~~
In function ‘mbuf_to_desc’,
inlined from ‘vhost_enqueue_async_packed’ at ../lib/vhost/virtio_net.c:1826:6,
inlined from ‘virtio_dev_rx_async_packed’ at ../lib/vhost/virtio_net.c:1840:6,
inlined from ‘virtio_dev_rx_async_submit_packed.constprop’ at ../lib/vhost/virtio_net.c:1900:7:
../lib/vhost/virtio_net.c:1161:35: error: ‘buf_vec[0].buf_len’ may be used uninitialized [-Werror=maybe-uninitialized]
1161 | buf_len = buf_vec[vec_idx].buf_len;
| ~~~~~~~~~~~~~~~~^~~~~~~~
../lib/vhost/virtio_net.c: In function ‘virtio_dev_rx_async_submit_packed.constprop’:
../lib/vhost/virtio_net.c:1838:27: note: ‘buf_vec’ declared here
1838 | struct buf_vector buf_vec[BUF_VECTOR_MAX];
| ^~~~~~~
cc1: all warnings being treated as errors
[476/3583] Compiling C object 'lib/76b5a35@@rte_port@sta/port_rte_port_kni.c.o'.
[477/3583] Compiling C object 'lib/76b5a35@@rte_pdump@sta/pdump_rte_pdump.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-shared-loongarch64" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2022-08-27 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220827085908.52080-8-zhoumin@loongson.cn>
2022-08-27 9:00 ` |WARNING| " checkpatch
2022-08-27 10:20 ` 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=20220827102001.16566-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.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).