From: Thomas Huth <thuth@redhat.com>
To: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>
Cc: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Subject: [PATCH v4 6/6] iotests: Enable more tests in the 'auto' group to improve test coverage
Date: Mon, 2 Dec 2019 11:10:39 +0100 [thread overview]
Message-ID: <20191202101039.8981-7-thuth@redhat.com> (raw)
In-Reply-To: <20191202101039.8981-1-thuth@redhat.com>
According to Kevin, tests 030, 040 and 041 are among the most valuable
tests that we have, so we should always run them if possible, even if
they take a little bit longer.
According to Max, it would be good to have a test for iothreads and
migration. 127 and 256 seem to be good candidates for iothreads. For
migration, let's enable 181 and 203 (which also tests iothreads).
(091 would be a good candidate for migration, too, but Alex Bennée
reported that this test fails on ZFS file systems, so it can't be
included yet)
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
tests/qemu-iotests/group | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests/group
index 6b10a6a762..2b56392e31 100644
--- a/tests/qemu-iotests/group
+++ b/tests/qemu-iotests/group
@@ -51,7 +51,7 @@
027 rw auto quick
028 rw backing quick
029 rw auto quick
-030 rw backing
+030 rw auto backing
031 rw auto quick
032 rw auto quick
033 rw auto quick
@@ -61,8 +61,8 @@
037 rw auto backing quick
038 rw auto backing quick
039 rw auto quick
-040 rw
-041 rw backing
+040 rw auto
+041 rw auto backing
042 rw auto quick
043 rw auto backing
044 rw
@@ -148,7 +148,7 @@
124 rw backing
125 rw
126 rw auto backing
-127 rw backing quick
+127 rw auto backing quick
128 rw quick
129 rw quick
130 rw quick
@@ -197,7 +197,7 @@
177 rw auto quick
178 img
179 rw auto quick
-181 rw migration
+181 rw auto migration
182 rw quick
183 rw migration
184 rw auto quick
@@ -218,7 +218,7 @@
200 rw
201 rw migration
202 rw quick
-203 rw migration
+203 rw auto migration
204 rw quick
205 rw quick
206 rw
@@ -270,7 +270,7 @@
253 rw quick
254 rw backing quick
255 rw quick
-256 rw quick
+256 rw auto quick
257 rw
258 rw quick
260 rw quick
--
2.18.1
next prev parent reply other threads:[~2019-12-02 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 10:10 [PATCH v4 0/6] Enable more iotests during "make check-block" Thomas Huth
2019-12-02 10:10 ` [PATCH v4 1/6] iotests: remove 'linux' from default supported platforms Thomas Huth
2019-12-02 10:10 ` [PATCH v4 2/6] iotests: Test 041 only works on certain systems Thomas Huth
2020-01-20 14:31 ` Max Reitz
2019-12-02 10:10 ` [PATCH v4 3/6] iotests: Test 183 does not work on macOS and OpenBSD Thomas Huth
2020-01-20 14:36 ` Max Reitz
2020-01-20 16:01 ` Thomas Huth
2019-12-02 10:10 ` [PATCH v4 4/6] iotests: Check for the availability of the required devices in 267 and 127 Thomas Huth
2020-01-20 14:47 ` Max Reitz
2019-12-02 10:10 ` [PATCH v4 5/6] iotests: Skip Python-based tests if QEMU does not support virtio-blk Thomas Huth
2020-01-20 14:50 ` Max Reitz
2020-01-20 16:05 ` Thomas Huth
2019-12-02 10:10 ` Thomas Huth [this message]
2020-01-20 14:51 ` [PATCH v4 6/6] iotests: Enable more tests in the 'auto' group to improve test coverage Max Reitz
2020-01-20 14:52 ` [PATCH v4 0/6] Enable more iotests during "make check-block" Max Reitz
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=20191202101039.8981-7-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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).