iotests/linters: Add entry point for linting via Python CI
authorJohn Snow <jsnow@redhat.com>
Tue, 19 Oct 2021 14:49:15 +0000 (10:49 -0400)
committerJohn Snow <jsnow@redhat.com>
Mon, 1 Nov 2021 15:54:59 +0000 (11:54 -0400)
commita4294435309d8429e8ee89908b5d7cebf6a648df
treefb31751ec27997046ce9533ddc7deb40a4221645
parentc293ba55c52ce07e03919e61e4a17d2cc2c944d4
iotests/linters: Add entry point for linting via Python CI

We need at least a tiny little shim here to join test file discovery
with test invocation. This logic could conceivably be hosted somewhere
in python/, but I felt it was strictly the least-rude thing to keep the
test logic here in iotests/, even if this small function isn't itself an
iotest.

Note that we don't actually even need the executable bit here, we'll be
relying on the ability to run this module as a script using Python CLI
arguments. No chance it gets misunderstood as an actual iotest that way.

(It's named, not in tests/, doesn't have the execute bit, and doesn't
have an execution shebang.)

Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Message-id: 20211019144918.3159078-13-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
tests/qemu-iotests/linters.py