automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 45f04d88ae8fa6217812abdaa623d66b05fc7b6a
Date: Fri, 05 Jan 2024 03:46:35 -0800 (PST)	[thread overview]
Message-ID: <6597ec1b.c80a0220.835a5.3786SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: 21.11-staging

45f04d88ae8fa6217812abdaa623d66b05fc7b6a --> testing fail

Test environment and result as below:

+-----------------------+--------------------+
|      Environment      | dpdk_meson_compile |
+=======================+====================+
| Fedora 38 (ARM Clang) | FAIL               |
+-----------------------+--------------------+
| Fedora 37 (ARM)       | FAIL               |
+-----------------------+--------------------+
| Fedora 38 (ARM)       | FAIL               |
+-----------------------+--------------------+
| Ubuntu 20.04 ARM SVE  | PASS               |
+-----------------------+--------------------+

==== 20 line log output for Fedora 38 (ARM) (dpdk_meson_compile): ====
../lib/vhost/virtio_net.c:940:18: error: 'buf_vec[0].buf_iova' may be used uninitialized [-Werror=maybe-uninitialized]
940 |         buf_iova = buf_vec[vec_idx].buf_iova;
|         ~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/vhost/virtio_net.c: In function 'virtio_dev_rx_async_submit_packed':
../lib/vhost/virtio_net.c:1618:27: note: 'buf_vec' declared here
1618 |         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:1606:6,
inlined from 'virtio_dev_rx_async_packed' at ../lib/vhost/virtio_net.c:1620:6,
inlined from 'virtio_dev_rx_async_submit_packed' at ../lib/vhost/virtio_net.c:1679:7:
../lib/vhost/virtio_net.c:941:35: error: 'buf_vec[0].buf_len' may be used uninitialized [-Werror=maybe-uninitialized]
941 |         buf_len = buf_vec[vec_idx].buf_len;
|                   ~~~~~~~~~~~~~~~~^~~~~~~~
../lib/vhost/virtio_net.c: In function 'virtio_dev_rx_async_submit_packed':
../lib/vhost/virtio_net.c:1618:27: note: 'buf_vec' declared here
1618 |         struct buf_vector buf_vec[BUF_VECTOR_MAX];
|                           ^~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27569/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-01-05 11:46 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 11:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-05 13:43 dpdklab
2024-01-05 13:29 dpdklab
2024-01-05 12:10 dpdklab
2024-01-05 12:08 dpdklab
2024-01-05 12:07 dpdklab
2024-01-05 12:05 dpdklab
2024-01-05 12:04 dpdklab
2024-01-05 12:03 dpdklab
2024-01-05 11:58 dpdklab
2024-01-05 11:58 dpdklab
2024-01-05 11:57 dpdklab
2024-01-05 11:57 dpdklab
2024-01-05 11:57 dpdklab
2024-01-05 11:57 dpdklab
2024-01-05 11:56 dpdklab
2024-01-05 11:55 dpdklab
2024-01-05 11:55 dpdklab
2024-01-05 11:55 dpdklab
2024-01-05 11:52 dpdklab
2024-01-05 11:51 dpdklab
2024-01-05 11:47 dpdklab
2024-01-05 11:46 dpdklab
2024-01-05 11:46 dpdklab
2024-01-05 11:45 dpdklab
2024-01-05 11:45 dpdklab
2024-01-05 11:44 dpdklab
2024-01-05 11:44 dpdklab
2024-01-05 11:44 dpdklab
2024-01-05 11:44 dpdklab
2024-01-05 11:43 dpdklab
2024-01-05 11:43 dpdklab
2024-01-05 11:43 dpdklab
2024-01-05 11:43 dpdklab
2024-01-05 11:42 dpdklab
2024-01-05 11:41 dpdklab
2024-01-05 11:41 dpdklab
2022-03-01  6:08 dpdklab
2022-02-12  6:08 dpdklab
2022-02-07 10:04 dpdklab
2022-01-28  7:39 dpdklab
2022-01-27 17:15 dpdklab
2022-01-27  7:37 dpdklab
2022-01-21 16:32 dpdklab
2022-01-21  8:20 dpdklab
2022-01-20  8:18 dpdklab
2022-01-14  6:09 dpdklab
2021-11-30 19:39 dpdklab
2021-11-30 19:38 dpdklab
2021-11-30 19:22 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=6597ec1b.c80a0220.835a5.3786SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).