From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com,
qemu-devel@nongnu.org, mreitz@redhat.com, den@openvz.org,
jsnow@redhat.com
Subject: [PATCH v8 0/5] Rework iotests/check
Date: Sun, 24 Jan 2021 00:04:23 +0300 [thread overview]
Message-ID: <20210123210428.27220-1-vsementsov@virtuozzo.com> (raw)
v8:
about linters:
I didn't modify 297, as Max already staged 297 modifications to test all files.
Also, now I have two complains:
+************* Module testenv
+testenv.py:158:4: R0915: Too many statements (53/50) (too-many-statements)
+************* Module testrunner
+testrunner.py:222:4: R0911: Too many return statements (7/6) (too-many-return-statements)
Success: no issues found in 5 source files
And I feel, I'm tired to refactor it now.. Probably we can ignore them in 297. Probably I can
do some refactoring as a follow-up.
findtests: grammar, wording, add Eric's r-b
testenv: commit msg adjusted
wording, grammar
missed env_variables added
add logic for searching qemu-system-*, if
qemu-system-{arch} is not exist
handle valgrind and MALLOC_PERTURB_
fix s/vmkd/vmdk/
testrunner: commit msg adjusted
wording
fix extra new lines in diff output
s/0/fd/
use class instead of namedtuple
don't handle MALLOC_PERTURB_
declare self._stack in __init__
change thistime to be float
handle KeyboardInterrupt
casenotrun init to ''
fix "output mismatch .. {f_bad}" to be f-string
smarter terminal color handling
check: wording, grammar, sheepdoG, exClude_groups
change valgrind to be simple boolean option and pass
it to TestEnv
handle group.local
check virtio-blk in iotests.py
add --color option
Vladimir Sementsov-Ogievskiy (5):
iotests: add findtests.py
iotests: add testenv.py
iotests: add testrunner.py
iotests: rewrite check into python
iotests: rename and move 169 and 199 tests
docs/devel/testing.rst | 50 +-
Makefile | 1 -
tests/check-block.sh | 2 +-
tests/qemu-iotests/check | 1095 ++---------------
tests/qemu-iotests/common.env.in | 3 -
tests/qemu-iotests/findtests.py | 159 +++
tests/qemu-iotests/group | 321 -----
tests/qemu-iotests/iotests.py | 8 +
tests/qemu-iotests/meson.build | 3 -
tests/qemu-iotests/testenv.py | 278 +++++
tests/qemu-iotests/testrunner.py | 366 ++++++
.../migrate-bitmaps-postcopy-test} | 0
.../migrate-bitmaps-postcopy-test.out} | 0
.../{169 => tests/migrate-bitmaps-test} | 0
.../migrate-bitmaps-test.out} | 0
15 files changed, 990 insertions(+), 1296 deletions(-)
delete mode 100644 tests/qemu-iotests/common.env.in
create mode 100644 tests/qemu-iotests/findtests.py
delete mode 100644 tests/qemu-iotests/group
create mode 100644 tests/qemu-iotests/testenv.py
create mode 100644 tests/qemu-iotests/testrunner.py
rename tests/qemu-iotests/{199 => tests/migrate-bitmaps-postcopy-test} (100%)
rename tests/qemu-iotests/{199.out => tests/migrate-bitmaps-postcopy-test.out} (100%)
rename tests/qemu-iotests/{169 => tests/migrate-bitmaps-test} (100%)
rename tests/qemu-iotests/{169.out => tests/migrate-bitmaps-test.out} (100%)
--
2.29.2
next reply other threads:[~2021-01-23 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 21:04 Vladimir Sementsov-Ogievskiy [this message]
2021-01-23 21:04 ` [PATCH v8 1/5] iotests: add findtests.py Vladimir Sementsov-Ogievskiy
2021-01-23 21:04 ` [PATCH v8 2/5] iotests: add testenv.py Vladimir Sementsov-Ogievskiy
2021-01-25 12:32 ` Vladimir Sementsov-Ogievskiy
2021-01-25 22:05 ` Kevin Wolf
2021-01-26 8:28 ` Vladimir Sementsov-Ogievskiy
2021-01-26 9:45 ` Kevin Wolf
2021-01-26 10:08 ` Vladimir Sementsov-Ogievskiy
2021-01-26 10:13 ` Kevin Wolf
2021-01-23 21:04 ` [PATCH v8 3/5] iotests: add testrunner.py Vladimir Sementsov-Ogievskiy
2021-01-23 21:04 ` [PATCH v8 4/5] iotests: rewrite check into python Vladimir Sementsov-Ogievskiy
2021-01-23 21:04 ` [PATCH v8 5/5] iotests: rename and move 169 and 199 tests Vladimir Sementsov-Ogievskiy
2021-01-25 16:08 ` [PATCH v8 0/5] Rework iotests/check Kevin Wolf
2021-01-25 16:23 ` Vladimir Sementsov-Ogievskiy
2021-01-25 16:36 ` Vladimir Sementsov-Ogievskiy
2021-01-25 16:50 ` Kevin Wolf
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=20210123210428.27220-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--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.