qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Cleber Rosa <crosa@redhat.com>
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] iotests: make 083 specific to raw
Date: Tue, 16 Oct 2018 14:51:10 +0200	[thread overview]
Message-ID: <20181016125110.GG5620@dhcp-200-186.str.redhat.com> (raw)
In-Reply-To: <20181015200319.23076-1-crosa@redhat.com>

Am 15.10.2018 um 22:03 hat Cleber Rosa geschrieben:
> While testing the Python 3 changes which touch the 083 test, I noticed
> that it would fail with qcow2.  Expanding the testing, I noticed it
> had nothing to do with the Python 3 changes, and in fact, it would not
> pass on anything but raw:
> 
>  raw: pass
>  bochs: not generic
>  cloop: not generic
>  parallels: fail
>  qcow: fail
>  qcow2: fail
>  qed: fail
>  vdi: fail
>  vhdx: fail
>  vmdk: fail
>  vpc: fail
>  luks: fail
> 
> The errors are a mixture I/O and "image not in xxx format", such as:
> 
>   === Check disconnect before data ===
> 
>   Unexpected end-of-file before all bytes were read
>  -read failed: Input/output error
>  +can't open device nbd+tcp://127.0.0.1:PORT/foo: Could not open 'nbd://127.0.0.1:PORT/foo': Input/output error
> 
>   === Check disconnect after data ===
> 
>  -read 512/512 bytes at offset 0
>  -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
>  +can't open device nbd+tcp://127.0.0.1:PORT/foo: Image not in qcow format
> 
> I'm not aware if there's a quick fix, so, for the time being, it looks
> like the honest approach is to make the test known to work on raw
> only.
> 
> Signed-off-by: Cleber Rosa <crosa@redhat.com>

Yes, that makes sense to me.

Thanks, applied to the block branch.

Kevin

      reply	other threads:[~2018-10-16 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 20:03 [Qemu-devel] [RFC PATCH] iotests: make 083 specific to raw Cleber Rosa
2018-10-16 12:51 ` Kevin Wolf [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=20181016125110.GG5620@dhcp-200-186.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.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).