iotests: Run pylint and mypy in a testcase
commit19b7868eff865c01985a5d37f1c9c0c8691b0001
authorKevin Wolf <kwolf@redhat.com>
Mon, 11 May 2020 16:35:29 +0000 (11 18:35 +0200)
committerKevin Wolf <kwolf@redhat.com>
Mon, 18 May 2020 17:05:25 +0000 (18 19:05 +0200)
tree7b42805b57f83fbaf4e750257949261683e29782
parentcd8f5b75927afdd8ac2378f4360208e0aa8f58e2
iotests: Run pylint and mypy in a testcase

We made sure that iotests.py passes pylint. It would be a shame if we
allowed new patches in that break this again, so let's just add a
meta-test case that runs pylint on it.

While we don't pass mypy --strict yet, we can already run it with a few
options that would be part of --strict to make sure that we won't
regress on these aspects at least until we can enable the full thing.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20200511163529.349329-3-kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
tests/qemu-iotests/297 [new file with mode: 0755]
tests/qemu-iotests/297.out [new file with mode: 0644]
tests/qemu-iotests/group