From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
vsementsov@virtuozzo.com, dgilbert@redhat.com,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: [PATCH for-5.1?] iotests: Adjust which tests are quick
Date: Mon, 27 Jul 2020 14:51:17 -0500 [thread overview]
Message-ID: <20200727195117.132151-1-eblake@redhat.com> (raw)
A quick run of './check -qcow2 -g migration' shows that test 169 is
NOT quick, but meanwhile several other tests ARE quick. Let's adjust
the test designations accordingly.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
I noticed this while working on my pending pull request that includes
Vladimir's massive speedup of 199 (but even with his speedup, that test
is still not quick).
tests/qemu-iotests/group | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests/group
index 1d0252e1f051..806044642c69 100644
--- a/tests/qemu-iotests/group
+++ b/tests/qemu-iotests/group
@@ -112,7 +112,7 @@
088 rw quick
089 rw auto quick
090 rw auto quick
-091 rw migration
+091 rw migration quick
092 rw quick
093 throttle
094 rw quick
@@ -186,7 +186,7 @@
162 quick
163 rw
165 rw quick
-169 rw quick migration
+169 rw migration
170 rw auto quick
171 rw quick
172 auto
@@ -197,9 +197,9 @@
177 rw auto quick
178 img
179 rw auto quick
-181 rw auto migration
+181 rw auto migration quick
182 rw quick
-183 rw migration
+183 rw migration quick
184 rw auto quick
185 rw
186 rw auto
@@ -216,9 +216,9 @@
198 rw
199 rw migration
200 rw
-201 rw migration
+201 rw migration quick
202 rw quick
-203 rw auto migration
+203 rw auto migration quick
204 rw quick
205 rw quick
206 rw
--
2.27.0
next reply other threads:[~2020-07-27 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 19:51 Eric Blake [this message]
2020-07-27 20:07 ` [PATCH for-5.1?] iotests: Adjust which tests are quick Vladimir Sementsov-Ogievskiy
2020-07-28 7:13 ` Thomas Huth
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=20200727195117.132151-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).