From: Thomas Huth <thuth@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org
Subject: [PATCH v2 5/6] iotests: Enable more tests in the 'auto' group to improve test coverage
Date: Mon, 21 Oct 2019 12:53:49 +0200 [thread overview]
Message-ID: <20191021105350.1710-6-thuth@redhat.com> (raw)
In-Reply-To: <20191021105350.1710-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 091, 181, 183, and 203 (which also tests
iothreads).
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
tests/qemu-iotests/group | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests/group
index a73df279e5..2dd671b82e 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
@@ -112,7 +112,7 @@
088 rw quick
089 rw auto quick
090 rw auto quick
-091 rw migration
+091 rw auto migration
092 rw quick
093 throttle
094 rw quick
@@ -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 auto quick
@@ -197,9 +197,9 @@
177 rw auto quick
178 img
179 rw auto quick
-181 rw migration
+181 rw auto migration
182 rw quick
-183 rw migration
+183 rw auto migration
184 rw auto quick
185 rw
186 rw auto
@@ -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-10-21 10:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 10:53 [PATCH v2 0/6] Enable more iotests during "make check-block" Thomas Huth
2019-10-21 10:53 ` [PATCH v2 1/6] iotests: remove 'linux' from default supported platforms Thomas Huth
2019-10-21 10:53 ` [PATCH v2 2/6] iotests: Test 041 only works on certain systems Thomas Huth
2019-10-21 10:53 ` [PATCH v2 3/6] iotests: Test 183 does not work on macOS and OpenBSD Thomas Huth
2019-10-21 10:53 ` [PATCH v2 4/6] iotests: Skip "make check-block" if QEMU does not support virtio-blk Thomas Huth
2019-10-21 10:53 ` Thomas Huth [this message]
2019-10-21 10:53 ` [PATCH v2 6/6] iotests: Remove 130 from the "auto" group Thomas Huth
2019-10-21 13:09 ` [PATCH v2 0/6] Enable more iotests during "make check-block" no-reply
2019-10-21 13:31 ` Thomas Huth
2019-10-21 17:03 ` no-reply
2019-10-21 17:03 ` no-reply
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=20191021105350.1710-6-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.