From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Jeff Cody <jcody@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] Failing iotests in v2.3.0-rc2 / master
Date: Sat, 11 Apr 2015 05:41:05 +0200 [thread overview]
Message-ID: <552897D1.7020300@suse.de> (raw)
Hi,
001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
033 is failing for -vhdx.
(Note that `make check-block` only tests -qcow2, so didn't uncover
either of them.)
Given a failing test, am I seeing correctly that there is no command
line option to skip this one failing test? -x seems to be for groups only.
Regards,
Andreas
$ ./check -v -T -qcow -g quick
[...]
001 6s ... [05:12:39]
$ ./check -v -T -vhdx -g quick
[...]
033 1s ... [04:06:09] [04:06:11] - output mismatch (see 033.out.bad)
--- /home/andreas/QEMU/qemu/tests/qemu-iotests/033.out 2015-04-08
20:19:11.947290578 +0200
+++ 033.out.bad 2015-04-11 04:06:11.939300375 +0200
@@ -2,52 +2,46 @@
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728
== preparing image ==
-wrote 1024/1024 bytes at offset 512
-1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 1536/1536 bytes at offset 131072
-1.500 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 131072/131072 bytes at offset 1024
-128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: Operation not supported
+write failed: Operation not supported
+write failed: Operation not supported
== verifying patterns (1) ==
+Pattern verification failed at offset 512, 512 bytes
read 512/512 bytes at offset 512
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
read 131072/131072 bytes at offset 1024
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+Pattern verification failed at offset 132096, 512 bytes
read 512/512 bytes at offset 132096
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
== rewriting zeroes ==
-wrote 65536/65536 bytes at offset 65536
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 65536/65536 bytes at offset 65536
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: Operation not supported
+write failed: Operation not supported
== verifying patterns (2) ==
read 131072/131072 bytes at offset 1024
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
== preparing image ==
-wrote 1024/1024 bytes at offset 512
-1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 1536/1536 bytes at offset 131072
-1.500 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 131072/131072 bytes at offset 1024
-128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: Operation not supported
+write failed: Operation not supported
+write failed: Operation not supported
== verifying patterns (1) ==
+Pattern verification failed at offset 512, 512 bytes
read 512/512 bytes at offset 512
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
read 131072/131072 bytes at offset 1024
128 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+Pattern verification failed at offset 132096, 512 bytes
read 512/512 bytes at offset 132096
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
== rewriting zeroes ==
-wrote 65536/65536 bytes at offset 65536
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 65536/65536 bytes at offset 65536
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+write failed: Operation not supported
+write failed: Operation not supported
== verifying patterns (2) ==
read 131072/131072 bytes at offset 1024
[...]
Not run: 017 018 019 020 024 025 027 028 029 031 034 035 036 037 038 039
042 045 046 047 048 050 053 054 058 059 060 062 063 065 066 067 068 069
071 073 074 075 077 078 081 082 084 086 087 088 089 090 092 094 095 098
101 102 103 107 108 110 111 113 114 116 123 128 130
Failures: 033
Failed 1 of 19 tests
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
next reply other threads:[~2015-04-11 3:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 3:41 Andreas Färber [this message]
2015-04-11 14:33 ` [Qemu-devel] Failing iotests in v2.3.0-rc2 / master Andreas Färber
2015-04-13 16:42 ` Paolo Bonzini
2015-04-13 15:29 ` John Snow
2015-04-13 17:03 ` Andreas Färber
2015-04-14 9:57 ` Kevin Wolf
2015-04-15 4:53 ` Jeff Cody
2015-04-15 9:26 ` Kevin Wolf
2015-04-15 9:34 ` Andreas Färber
2015-04-15 9:47 ` Kevin Wolf
2015-04-15 9:54 ` Andreas Färber
2015-04-15 11:27 ` Jeff Cody
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=552897D1.7020300@suse.de \
--to=afaerber@suse.de \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).