From: no-reply@patchew.org
To: eric.auger@redhat.com
Cc: fam@euphon.net, eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
alex.williamson@redhat.com, aik@ozlabs.ru, groug@kaod.org
Subject: Re: [Qemu-devel] [PATCH v2] hw/vfio/common: Refactor container initialization
Date: Wed, 23 Jan 2019 06:23:03 -0800 (PST) [thread overview]
Message-ID: <154825338186.21.2661799743092991292@ebba9967afc0> (raw)
In-Reply-To: <20190117210245.18364-1-eric.auger@redhat.com>
Patchew URL: https://patchew.org/QEMU/20190117210245.18364-1-eric.auger@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
time make docker-test-mingw@fedora SHOW_ENV=1 J=14
=== TEST SCRIPT END ===
CC job-qmp.o
CC qdev-monitor.o
/tmp/qemu-test/src/block/sheepdog.c: In function 'find_vdi_name':
/tmp/qemu-test/src/block/sheepdog.c:1239:5: error: 'strncpy' specified bound 256 equals destination size [-Werror=stringop-truncation]
strncpy(buf + SD_MAX_VDI_LEN, tag, SD_MAX_VDI_TAG_LEN);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
The full log is available at
http://patchew.org/logs/20190117210245.18364-1-eric.auger@redhat.com/testing.docker-mingw@fedora/?type=message.
---
Email generated automatically by Patchew [http://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2019-01-23 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 21:02 [Qemu-devel] [PATCH v2] hw/vfio/common: Refactor container initialization Eric Auger
2019-01-18 4:51 ` Alexey Kardashevskiy
2019-01-18 8:52 ` Auger Eric
2019-01-18 8:52 ` Greg Kurz
2019-01-23 14:23 ` no-reply [this message]
2019-01-23 14:44 ` Auger Eric
2019-01-23 15:01 ` Eric Blake
2019-01-23 15:31 ` Auger Eric
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=154825338186.21.2661799743092991292@ebba9967afc0 \
--to=no-reply@patchew.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=fam@euphon.net \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.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 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.