qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: TianShan Wong <tianshan.wong@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-iotests: qcow2 failed for test 026 038
Date: Mon, 20 May 2013 08:22:58 +0200	[thread overview]
Message-ID: <CAJSP0QUSC94q2Lvoy8NQXj5Z3sdzb1E-kQKM4mpH+a6ciuPCVg@mail.gmail.com> (raw)
In-Reply-To: <51986DDD.8010503@gmail.com>

On Sun, May 19, 2013 at 8:14 AM, TianShan Wong <tianshan.wong@gmail.com> wrote:
> I am testing qcow2 with qemu-iotests on F17, using upstream QEMU source
> tree:
> $ uname -a
> Linux Test.Server 3.8.12-100.fc17.x86_64 #1 SMP Wed May 8 15:36:14 UTC 2013
> x86_64 x86_64 x86_64 GNU/Linux
>
> But got failed result as follows:
>
> $ ./check -qcow2
[...]
> Not run: 006 016 045
> Failures: 026 038
> Failed 2 of 49 tests

Thanks for reporting this.  Unfortunately they are known failures:

The precise leaked clusters number tends to change over time as qcow2
code is modified - for example, changes to the error code paths may
affect the leaked clusters in a particular scenario.

The output of the aio test is non-deterministic, I get a similar
"failure" here and it's simply a different interleaving of outputs -
the actual test is succeeding.

Fixing this is on my todo list and probably Kevin's too.  If you have
time to send patches, that would be excellent too.

Stefan

      reply	other threads:[~2013-05-20  6:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19  6:14 [Qemu-devel] qemu-iotests: qcow2 failed for test 026 038 TianShan Wong
2013-05-20  6:22 ` Stefan Hajnoczi [this message]

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=CAJSP0QUSC94q2Lvoy8NQXj5Z3sdzb1E-kQKM4mpH+a6ciuPCVg@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tianshan.wong@gmail.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).