All of lore.kernel.org
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: stefanha@redhat.com
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
	qemu-block@nongnu.org, mst@redhat.com, qemu-devel@nongnu.org,
	mreitz@redhat.com, stefanha@redhat.com
Subject: Re: [PULL 0/2] Block patches
Date: Wed, 25 Sep 2019 23:16:31 -0700 (PDT)	[thread overview]
Message-ID: <156947859030.9841.4795650725800418297@8230166b0665> (raw)
In-Reply-To: <20190925174400.8578-1-stefanha@redhat.com>

Patchew URL: https://patchew.org/QEMU/20190925174400.8578-1-stefanha@redhat.com/



Hi,

This series failed the docker-mingw@fedora build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.

=== TEST SCRIPT BEGIN ===
#! /bin/bash
export ARCH=x86_64
make docker-image-fedora V=1 NETWORK=1
time make docker-test-mingw@fedora J=14 NETWORK=1
=== TEST SCRIPT END ===

  CC      authz/list.o
  CC      authz/listfile.o
/tmp/qemu-test/src/util/iov.c: In function 'qemu_iovec_init_extended':
/tmp/qemu-test/src/util/iov.c:451:9: error: 'mid_iov' may be used uninitialized in this function [-Werror=maybe-uninitialized]
         memcpy(p, mid_iov, mid_niov * sizeof(*p));
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors


The full log is available at
http://patchew.org/logs/20190925174400.8578-1-stefanha@redhat.com/testing.docker-mingw@fedora/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com

  parent reply	other threads:[~2019-09-26  6:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 17:43 [PULL 0/2] Block patches Stefan Hajnoczi
2019-09-25 17:43 ` [PULL 1/2] util/ioc.c: try to reassure Coverity about qemu_iovec_init_extended Stefan Hajnoczi
2019-09-26 10:54   ` Vladimir Sementsov-Ogievskiy
2019-09-25 17:44 ` [PULL 2/2] virtio-blk: schedule virtio_notify_config to run on main context Stefan Hajnoczi
2019-09-26  6:16 ` no-reply [this message]
2019-09-26 12:06   ` [PULL 0/2] Block patches Vladimir Sementsov-Ogievskiy
2019-09-26 12:56 ` Peter Maydell
2019-10-25 19:18 Stefan Hajnoczi
2019-10-26  9:13 ` Peter Maydell
2019-12-13 14:33 Stefan Hajnoczi
2019-12-13 21:10 ` Peter Maydell
2020-02-10  9:23 Stefan Hajnoczi
2020-02-10 18:09 ` Peter Maydell
2021-03-24 14:52 Stefan Hajnoczi
2021-03-24 18:05 ` Peter Maydell
2021-03-24 20:18   ` Vladimir Sementsov-Ogievskiy
2021-03-24 20:42     ` Peter Maydell
2021-03-25  9:56       ` Stefan Hajnoczi
2021-03-25 10:17         ` Vladimir Sementsov-Ogievskiy
2021-03-25 16:28           ` Stefan Hajnoczi
2021-03-25 16:36             ` Peter Maydell
2021-03-25 17:40               ` Stefan Hajnoczi
2021-03-26 10:22 ` Peter Maydell
2021-10-11 12:40 Stefan Hajnoczi
2021-10-11 18:23 ` Richard Henderson
2022-07-07  8:12 Stefan Hajnoczi
2022-07-07 10:51 ` Richard Henderson
2023-04-24 17:55 Stefan Hajnoczi
2023-04-25 11:15 ` Richard Henderson
2024-01-22 16:01 Stefan Hajnoczi
2024-01-25 15:11 ` Peter Maydell
2024-01-25 15:47 ` Michael Tokarev

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=156947859030.9841.4795650725800418297@8230166b0665 \
    --to=no-reply@patchew.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.