From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/5] iotests: Make some tests less flaky
Date: Thu, 9 Nov 2017 21:30:20 +0100 [thread overview]
Message-ID: <20171109203025.27493-1-mreitz@redhat.com> (raw)
There are a couple of tests that fail (on my machine) from time to
time (and by that I mean that recently I've rarely ever had a test run
with both 083 and 136 working on first try).
This series should fix most (at least the issues I am aware of).
Notes:
- 083 might have another issue, but if so it occurs extremely rarely and
so I was unable to debug it.
- 129 is flaky, too, because it tries to use block jobs with BB
throttling -- however, block jobs ignore that these days. Making it
use a throttle filter node will require quite a bit of work. See
http://lists.nongnu.org/archive/html/qemu-block/2017-11/msg00111.html
for more.
- 194 sometimes hangs because the source VM fails to drain its drive.
This is probably not an issue with the test, but actually an issue in
qemu. See
http://lists.nongnu.org/archive/html/qemu-block/2017-11/msg00256.html
for more.
v2:
- Spelling fixes [Eric]
- Contract grep | sed to a single sed in 083 [Eric]
git-backport-diff against v1:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/5:[----] [--] 'iotests: Make 030 less flaky'
002/5:[----] [--] 'iotests: Add missing 'blkdebug::' in 040'
003/5:[----] [--] 'iotests: Make 055 less flaky'
004/5:[0003] [FC] 'iotests: Make 083 less flaky'
005/5:[----] [--] 'iotests: Make 136 less flaky'
Max Reitz (5):
iotests: Make 030 less flaky
iotests: Add missing 'blkdebug::' in 040
iotests: Make 055 less flaky
iotests: Make 083 less flaky
iotests: Make 136 less flaky
tests/qemu-iotests/030 | 8 ++++++--
tests/qemu-iotests/040 | 2 +-
tests/qemu-iotests/055 | 25 ++++++++++++++++---------
tests/qemu-iotests/083 | 4 +++-
tests/qemu-iotests/136 | 14 +++++++++++++-
5 files changed, 39 insertions(+), 14 deletions(-)
--
2.13.6
next reply other threads:[~2017-11-09 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 20:30 Max Reitz [this message]
2017-11-09 20:30 ` [Qemu-devel] [PATCH v2 1/5] iotests: Make 030 less flaky Max Reitz
2017-11-09 20:30 ` [Qemu-devel] [PATCH v2 2/5] iotests: Add missing 'blkdebug::' in 040 Max Reitz
2017-11-09 20:30 ` [Qemu-devel] [PATCH v2 3/5] iotests: Make 055 less flaky Max Reitz
2017-11-09 20:30 ` [Qemu-devel] [PATCH v2 4/5] iotests: Make 083 " Max Reitz
2017-11-09 20:58 ` Eric Blake
2017-11-09 21:00 ` Max Reitz
2017-11-10 10:02 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-11-10 15:18 ` Max Reitz
2017-11-10 15:51 ` Alberto Garcia
2017-11-10 17:29 ` Max Reitz
2017-11-10 18:26 ` Eric Blake
2017-11-09 20:30 ` [Qemu-devel] [PATCH v2 5/5] iotests: Make 136 " Max Reitz
2017-11-09 22:29 ` [Qemu-devel] [PATCH v2 0/5] iotests: Make some tests " 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=20171109203025.27493-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.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).