From: Paolo Bonzini <pbonzini@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] iotest 026 -nocache is broken
Date: Tue, 22 Mar 2016 19:06:23 +0100 [thread overview]
Message-ID: <56F1899F.304@redhat.com> (raw)
In-Reply-To: <56F1883B.6080901@virtuozzo.com>
On 22/03/2016 19:00, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> Just a notice
>
> for commit (near to master branch top)
> commit 3666a97f78704b941c360dc917acb14c8774eca7
> Author: Eric Blake <eblake@redhat.com>
> Date: Thu Mar 17 16:48:40 2016 -0600
>
> qapi: Use anonymous bases in QMP flat unions
>
> ./configure --target-list=x86_64-softmmu
>
> ...
>
> ./check -T -nocache -qcow2 026
>
> gives a lot of
> +Failed to flush the L2 table cache: No space left on device
> +Failed to flush the refcount block cache: No space left on device
>
> and some other differences.
>
> this affects ./tests/check-block.sh
>
> I've failed to find commit, for which this test was working..
>
> it fails even for the first commit, where 026.out.nocache was introduced:
>
> commit 8f94b077877151de93a63c73f796897309568ddb
> Author: Kevin Wolf <kwolf@redhat.com>
> Date: Wed Sep 4 13:16:05 2013 +0200
>
> qemu-iotests: Fixed test case 026
>
>
> May be I'm doing something wrong, but I can't imagine what..
This test fails with different error messages depending on whether you
use nocache or writethrough.
Paolo
next prev parent reply other threads:[~2016-03-22 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 18:00 [Qemu-devel] iotest 026 -nocache is broken Vladimir Sementsov-Ogievskiy
2016-03-22 18:06 ` Paolo Bonzini [this message]
2016-03-23 9:58 ` Vladimir Sementsov-Ogievskiy
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=56F1899F.304@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).