qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, Fam Zheng <famz@redhat.com>,
	jcody@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 0/8] Implement reference count for BlockDriverState [resend]
Date: Mon, 26 Aug 2013 09:40:59 +0200	[thread overview]
Message-ID: <20130826074059.GA28566@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <5216C641.5020106@linux.vnet.ibm.com>

On Fri, Aug 23, 2013 at 10:17:37AM +0800, Wenchao Xia wrote:
>   What is the correct steps to run full qemu-iotests?
> I modified qemu-iotests-quick.sh as:
> 
> #!/bin/sh
> 
> # We don't know which of the system emulator binaries there is (or
> if there is
> # any at all), so the 'quick' group doesn't contain any tests that require
> # running qemu proper. Assign a fake binary name so that
> qemu-iotests doesn't
> # complain about the missing binary.
> export QEMU_PROG="$(pwd)/x86_64-softmmu/qemu-system-x86_64"
> 
> export QEMU_IMG_PROG="$(pwd)/qemu-img"
> export QEMU_IO_PROG="$(pwd)/qemu-io"
> export QEMU_NBD_PROG="$(pwd)/qemu-nbd"
> 
> cd $SRC_PATH/tests/qemu-iotests
> 
> ret=0
> ./check -T -nocache -qcow2 || ret=1
> 
> exit $ret
> 
>   Then make check-block, 026 038 fail, 038 sometimes fail.
> The code from is upstream, host is RH6.3 @ x86_64. Do I missed some
> steps?

You are running it correctly.

There are a couple of known failures in qemu-iotests.  It would be good
to fix them but no one has posted patches so far.  If in doubt, run
qemu-iotests on qemu.git/master to see which tests are known failures.

Stefan

      reply	other threads:[~2013-08-26  7:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 10:01 [Qemu-devel] [PATCH v5 0/8] Implement reference count for BlockDriverState [resend] Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 1/8] vvfat: use bdrv_new() to allocate BlockDriverState Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 2/8] iscsi: use bdrv_new() instead of stack structure Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 3/8] block: implement reference count for BlockDriverState Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 4/8] block: make bdrv_delete() static Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 5/8] migration: omit drive ref as we have bdrv_ref now Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 6/8] xen_disk: simplify blk_disconnect with refcnt Fam Zheng
2013-08-09 10:02 ` [Qemu-devel] [PATCH v5 7/8] nbd: use BlockDriverState refcnt Fam Zheng
2013-08-09 10:02 ` [Qemu-devel] [PATCH v5 8/8] block: use BDS ref for block jobs Fam Zheng
2013-08-22 11:38 ` [Qemu-devel] [PATCH v5 0/8] Implement reference count for BlockDriverState [resend] Stefan Hajnoczi
2013-08-23  1:01   ` Fam Zheng
2013-08-23  2:17   ` Wenchao Xia
2013-08-26  7:40     ` 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=20130826074059.GA28566@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=xiawenc@linux.vnet.ibm.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).