From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v4 0/4] iotests: use python logging
Date: Wed, 11 Sep 2019 20:16:29 -0400 [thread overview]
Message-ID: <20190912001633.11372-1-jsnow@redhat.com> (raw)
This series uses python logging to enable output conditionally on
iotests.log(). We unify an initialization call (which also enables
debugging output for those tests with -d) and then make the switch
inside of iotests.
It will help alleviate the need to create logged/unlogged versions
of all the various helpers we have made.
V4:
- Rebased on top of kwolf/block at the behest of mreitz
V3:
- Rebased for 4.1+; now based on main branch.
V2:
- Added all of the other python tests I missed to use script_initialize
- Refactored the common setup as per Ehabkost's suggestion
- Added protocol arguments to common initialization,
but this isn't strictly required.
John Snow (4):
iotests: add script_initialize
iotest 258: use script_main
iotests: specify protocol support via initialization info
iotests: use python logging for iotests.log()
tests/qemu-iotests/030 | 4 +-
tests/qemu-iotests/149 | 3 +-
tests/qemu-iotests/194 | 3 +-
tests/qemu-iotests/202 | 3 +-
tests/qemu-iotests/203 | 3 +-
tests/qemu-iotests/206 | 2 +-
tests/qemu-iotests/207 | 4 +-
tests/qemu-iotests/208 | 2 +-
tests/qemu-iotests/209 | 2 +-
tests/qemu-iotests/210 | 4 +-
tests/qemu-iotests/211 | 4 +-
tests/qemu-iotests/212 | 4 +-
tests/qemu-iotests/213 | 4 +-
tests/qemu-iotests/216 | 3 +-
tests/qemu-iotests/218 | 2 +-
tests/qemu-iotests/219 | 2 +-
tests/qemu-iotests/222 | 5 +-
tests/qemu-iotests/224 | 3 +-
tests/qemu-iotests/228 | 3 +-
tests/qemu-iotests/234 | 3 +-
tests/qemu-iotests/235 | 4 +-
tests/qemu-iotests/236 | 2 +-
tests/qemu-iotests/237 | 2 +-
tests/qemu-iotests/238 | 2 +
tests/qemu-iotests/242 | 2 +-
tests/qemu-iotests/245 | 1 +
tests/qemu-iotests/245.out | 24 ++++----
tests/qemu-iotests/246 | 2 +-
tests/qemu-iotests/248 | 2 +-
tests/qemu-iotests/254 | 2 +-
tests/qemu-iotests/255 | 2 +-
tests/qemu-iotests/256 | 2 +-
tests/qemu-iotests/258 | 8 +--
tests/qemu-iotests/262 | 3 +-
tests/qemu-iotests/iotests.py | 108 +++++++++++++++++++++-------------
35 files changed, 123 insertions(+), 106 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-12 0:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 0:16 John Snow [this message]
2019-09-12 0:16 ` [Qemu-devel] [PATCH v4 1/4] iotests: add script_initialize John Snow
2019-09-16 14:56 ` Vladimir Sementsov-Ogievskiy
2019-09-16 16:32 ` John Snow
2019-09-16 16:39 ` Vladimir Sementsov-Ogievskiy
2019-09-16 17:13 ` John Snow
2019-09-17 22:29 ` John Snow
2019-09-18 10:30 ` Vladimir Sementsov-Ogievskiy
2019-09-18 16:44 ` Vladimir Sementsov-Ogievskiy
2019-09-18 17:00 ` John Snow
2019-09-18 13:05 ` Thomas Huth
2019-09-18 18:41 ` John Snow
2019-09-12 0:16 ` [Qemu-devel] [PATCH v4 2/4] iotest 258: use script_main John Snow
2019-09-17 9:36 ` Vladimir Sementsov-Ogievskiy
2019-09-12 0:16 ` [Qemu-devel] [PATCH v4 3/4] iotests: specify protocol support via initialization info John Snow
2019-09-17 9:51 ` Vladimir Sementsov-Ogievskiy
2019-09-12 0:16 ` [Qemu-devel] [PATCH v4 4/4] iotests: use python logging for iotests.log() John Snow
2019-09-17 11:35 ` Vladimir Sementsov-Ogievskiy
2019-09-17 19:46 ` John Snow
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=20190912001633.11372-1-jsnow@redhat.com \
--to=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).