qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: Fam Zheng <famz@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Status and RFC of patchew testings on QEMU
Date: Mon, 17 Jul 2017 15:40:45 +0200	[thread overview]
Message-ID: <7cdcea0f-5c26-4e18-d7f0-fa11606ba2c9@redhat.com> (raw)
In-Reply-To: <20170717113115.GE5301@noname.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

On 2017-07-17 13:31, Kevin Wolf wrote:
> Am 17.07.2017 um 12:49 hat Peter Maydell geschrieben:
>> On 17 July 2017 at 11:39, Kevin Wolf <kwolf@redhat.com> wrote:
>>> Only today I noticed again that two recently merged pull requests broke
>>> qemu-iotests cases, so I must assume that apart from some block
>>> maintainers, nobody runs it regularly.
>>
>> If "make check" doesn't run it, it doesn't get run :-)
>> I actually looked into trying to run qemu-iotests tests
>> for the recent patches I sent for vpc and vmdk image format
>> handler fixes, but I couldn't get it to do anything sensible
>> and I couldn't find any documentation, so I gave up and
>> assumed that "make check" plus manual testing was good enough...
> 
> I think we had it in 'make check' for a while, but I seem to remember
> that people complained about things like the disk space that some of the
> tests needed for temporary files, and some exotic systems didn't support
> sparse files or something like that.

Wasn't that exotic system HFS+ on OS X/macOS? As far as I'm informed,
macOS has recently switched to APFS which does have sparse files (and I
think they have automatically converted running systems to APFS).

Max



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]

  reply	other threads:[~2017-07-17 13:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17  6:35 [Qemu-devel] Status and RFC of patchew testings on QEMU Fam Zheng
2017-07-17  9:05 ` Stefan Hajnoczi
2017-07-17  9:28   ` Peter Maydell
2017-07-17  9:39     ` Fam Zheng
2017-07-17 10:06       ` Peter Maydell
2017-07-17 10:26         ` Daniel P. Berrange
2017-07-25  9:58           ` Peter Maydell
2017-07-27 11:03             ` Fam Zheng
2017-07-27 11:30               ` Gerd Hoffmann
2017-07-17 10:03   ` Daniel P. Berrange
2017-07-17  9:41 ` Thomas Huth
2017-07-17 10:20   ` Daniel P. Berrange
2017-07-17 11:00     ` Peter Maydell
2017-07-17 11:06       ` Daniel P. Berrange
2017-07-28  5:59     ` Philippe Mathieu-Daudé
2017-07-17 23:17   ` Fam Zheng
2017-07-18  9:11     ` Thomas Huth
2017-07-18  9:37       ` Peter Maydell
2017-07-18  9:42         ` Daniel P. Berrange
2017-07-19  7:46           ` Fam Zheng
2017-07-17 10:02 ` Daniel P. Berrange
2017-07-21  3:24   ` Fam Zheng
2017-07-17 10:39 ` Kevin Wolf
2017-07-17 10:49   ` Peter Maydell
2017-07-17 11:31     ` Kevin Wolf
2017-07-17 13:40       ` Max Reitz [this message]
2017-07-28  5:56         ` Philippe Mathieu-Daudé
2017-07-17 23:28   ` Fam Zheng
2017-07-18 10:14     ` Daniel P. Berrange
2017-07-28  5:46 ` Philippe Mathieu-Daudé
2017-07-28  6:33   ` Fam Zheng
2017-07-28  7:18     ` Cornelia Huck

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=7cdcea0f-5c26-4e18-d7f0-fa11606ba2c9@redhat.com \
    --to=mreitz@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.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 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).