From: Thomas Huth <thuth@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: [PATCH 0/9] tests/qemu-iotests: Fix running with "check -ssh -qcow2"
Date: Fri, 15 Mar 2024 12:10:59 +0100 [thread overview]
Message-ID: <20240315111108.153201-1-thuth@redhat.com> (raw)
I recently wanted to check for some changes that I did to the URI handling
in the block layer code, but I had to discover that a lot of iotests only
work with the raw file format when using a protocol that is not "file",
i.e. "./check -ssh -qcow2" shows a lot of failures.
While some tests could be fixed to work with the "ssh" protocol, too,
many other tests seem to be written for the "file" protocol only and
thus have to be marked accordingly.
After applying these patches, there is still one failure left in test 181
where I'm unsure whether it's a real bug or whether this test should also
simply be marked to work with the "file" protocol only. Suggestions are
welcome!
Thomas Huth (9):
tests/qemu-iotests: Fix test 033 for running with non-file protocols
tests/qemu-iotests: Restrict test 066 to the 'file' protocol
tests/qemu-iotests: Restrict test 114 to the 'file' protocol
tests/qemu-iotests: Restrict test 130 to the 'file' protocol
tests/qemu-iotests: Restrict test 134 and 158 to the 'file' protocol
tests/qemu-iotests: Restrict test 156 to the 'file' protocol
tests/qemu-iotests: Restrict tests that use --image-opts to the 'file'
protocol
tests/qemu-iotests: Fix some tests that use --image-opts for other
protocols
tests/qemu-iotests: Restrict tests using "--blockdev file" to the file
protocol
tests/qemu-iotests/033 | 6 +++---
tests/qemu-iotests/066 | 2 +-
tests/qemu-iotests/114 | 2 +-
tests/qemu-iotests/130 | 2 +-
tests/qemu-iotests/134 | 2 +-
tests/qemu-iotests/156 | 2 +-
tests/qemu-iotests/158 | 2 +-
tests/qemu-iotests/188 | 2 +-
tests/qemu-iotests/189 | 2 +-
tests/qemu-iotests/198 | 2 +-
tests/qemu-iotests/263 | 6 ++++--
tests/qemu-iotests/284 | 7 +++----
tests/qemu-iotests/tests/detect-zeroes-registered-buf | 4 +++-
tests/qemu-iotests/tests/qcow2-internal-snapshots | 2 +-
tests/qemu-iotests/tests/qsd-jobs | 2 +-
15 files changed, 24 insertions(+), 21 deletions(-)
--
2.44.0
next reply other threads:[~2024-03-15 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 11:10 Thomas Huth [this message]
2024-03-15 11:11 ` [PATCH 1/9] tests/qemu-iotests: Fix test 033 for running with non-file protocols Thomas Huth
2024-03-15 11:11 ` [PATCH 2/9] tests/qemu-iotests: Restrict test 066 to the 'file' protocol Thomas Huth
2024-03-15 11:11 ` [PATCH 3/9] tests/qemu-iotests: Restrict test 114 " Thomas Huth
2024-03-15 11:11 ` [PATCH 4/9] tests/qemu-iotests: Restrict test 130 " Thomas Huth
2024-03-15 11:11 ` [PATCH 5/9] tests/qemu-iotests: Restrict test 134 and 158 " Thomas Huth
2024-03-15 11:11 ` [PATCH 6/9] tests/qemu-iotests: Restrict test 156 " Thomas Huth
2024-03-15 11:11 ` [PATCH 7/9] tests/qemu-iotests: Restrict tests that use --image-opts " Thomas Huth
2024-03-15 11:11 ` [PATCH 8/9] tests/qemu-iotests: Fix some tests that use --image-opts for other protocols Thomas Huth
2024-03-15 11:11 ` [PATCH 9/9] tests/qemu-iotests: Restrict tests using "--blockdev file" to the file protocol Thomas Huth
2024-03-18 12:14 ` [PATCH 0/9] tests/qemu-iotests: Fix running with "check -ssh -qcow2" Kevin Wolf
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=20240315111108.153201-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@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).