From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
qemu-devel@nongnu.org
Subject: [PATCH v2 0/2] pylint: fix new errors and warnings in qemu-iotests
Date: Fri, 8 Oct 2021 02:28:19 -0400 [thread overview]
Message-ID: <20211008062821.1010967-1-eesposit@redhat.com> (raw)
There are some warnings and errors that we either miss or
are new in pylint. Anyways, test 297 of qemu-iotests fails
because of that, so we need to fix it.
All these fixes involve just indentation or additional spaces
added.
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
---
v2:
* temporarly enable and then disable "bad whitespace" error in image-fleecing
* better indentation for a fix in test 129 in patch one
Emanuele Giuseppe Esposito (2):
pylint: fix errors and warnings generated by tests/qemu-iotests/297
qemu-iotests: fix image-fleecing pylint errors
tests/qemu-iotests/129 | 18 +++++++++---------
tests/qemu-iotests/310 | 16 ++++++++--------
tests/qemu-iotests/check | 11 ++++++-----
tests/qemu-iotests/iotests.py | 7 ++++---
tests/qemu-iotests/tests/image-fleecing | 8 ++++++--
5 files changed, 33 insertions(+), 27 deletions(-)
--
2.27.0
next reply other threads:[~2021-10-08 6:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 6:28 Emanuele Giuseppe Esposito [this message]
2021-10-08 6:28 ` [PATCH v2 1/2] pylint: fix errors and warnings generated by tests/qemu-iotests/297 Emanuele Giuseppe Esposito
2021-10-08 6:28 ` [PATCH v2 2/2] qemu-iotests: fix image-fleecing pylint errors Emanuele Giuseppe Esposito
2021-10-11 9:29 ` [PATCH v2 0/2] pylint: fix new errors and warnings in qemu-iotests Hanna Reitz
2021-10-11 9:58 ` Emanuele Giuseppe Esposito
2021-10-11 11:04 ` Hanna Reitz
2021-10-26 18:50 ` 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=20211008062821.1010967-1-eesposit@redhat.com \
--to=eesposit@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@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).