From: Richard Henderson <richard.henderson@linaro.org>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Cc: Hanna Czenczek <hreitz@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
Kevin Wolf <kwolf@redhat.com>
Subject: Re: io-qcow2 failures on zfs
Date: Fri, 26 May 2023 08:47:18 -0700 [thread overview]
Message-ID: <144e2ab5-8fe4-3b4a-7776-5722380b8616@linaro.org> (raw)
In-Reply-To: <333138b6-401b-d863-c2cf-90e36d16cc97@redhat.com>
On 5/26/23 01:02, Thomas Huth wrote:
> What output do you get when running the tests directly? i.e.:
>
> cd tests/qemu-iotests/
> ./check -qcow2 150
=== Mapping non-sparse conversion ===
Offset Length File
-0 0x100000 TEST_DIR/t.IMGFMT
+0 0x10000 TEST_DIR/t.IMGFMT
> ./check -qcow2 copy-before-write
+======================================================================
+FAIL: test_timeout_break_guest (__main__.TestCbwError)
+----------------------------------------------------------------------
+Traceback (most recent call last):
+ File "/home/richard.henderson/qemu/src/tests/qemu-iotests/tests/copy-before-write",
line 200, in test_timeout_break_guest
+ self.assertEqual(log, """\
+AssertionError: 'write failed: Connection timed out\nwrite f[121 chars]c)\n' != 'wrote
524288/524288 bytes at offset 0\n512 [182 chars]c)\n'
> ./check -qcow2 244
-[{ "start": 0, "length": 2097152, "depth": 0, "present": true, "zero": false, "data":
true, "offset": 0},
+[{ "start": 0, "length": 1048576, "depth": 0, "present": true, "zero": true, "data":
true, "offset": 0},
+{ "start": 1048576, "length": 1048576, "depth": 0, "present": true, "zero": false,
"data": true, "offset": 1048576},
{ "start": 2097152, "length": 2097152, "depth": 0, "present": true, "zero": true,
"data": false},
{ "start": 4194304, "length": 2097152, "depth": 0, "present": true, "zero": true,
"data": false, "offset": 4194304},
-{ "start": 6291456, "length": 60817408, "depth": 0, "present": true, "zero": false,
"data": true, "offset": 6291456}]
+{ "start": 6291456, "length": 60817408, "depth": 0, "present": true, "zero": true,
"data": true, "offset": 6291456}]
r~
prev parent reply other threads:[~2023-05-26 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 22:44 io-qcow2 failures on zfs Richard Henderson
2023-05-25 18:29 ` Richard Henderson
2023-05-26 8:02 ` Thomas Huth
2023-05-26 15:47 ` Richard Henderson [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=144e2ab5-8fe4-3b4a-7776-5722380b8616@linaro.org \
--to=richard.henderson@linaro.org \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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).