From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Cleber Rosa <crosa@redhat.com>, Hanna Reitz <hreitz@redhat.com>
Subject: Re: [PATCH 0/4] python: update linting for new mypy/pylint releases
Date: Wed, 6 Nov 2024 10:57:23 +0100 [thread overview]
Message-ID: <Zys9g8akOqlpuMQx@redhat.com> (raw)
In-Reply-To: <20241101173700.965776-1-jsnow@redhat.com>
Am 01.11.2024 um 18:36 hat John Snow geschrieben:
> Various python tests in the "check-python-tox" test case on GitLab have
> begun failing due to newer package versions. This patch set corrects
> those issues and also improves the reliability of local developer tests
> which may be using these tooling versions outside of GitLab pinned
> version tests.
>
> There are remaining issues with the "check-dev" test I have yet to
> rectify, but appear unrelated to linter versions specifically and will
> be handled separately.
>
> As a result of this patch, the optionally-run and may-fail
> "check-python-tox" test case on GitLab will become green again, and
> local invocations of "make check-tox" in the python subdirectory will
> also pass again. "check-python-minreqs" on GitLab and "make
> check-minreqs" in the local developer environment were/are
> unaffected. local iotest invocations for test case #297 ought to now
> begin passing on developer workstations with bleeding-edge python
> packages.
>
> John Snow (4):
> iotests: reflow ReproducibleTestRunner arguments
> iotests: correct resultclass type in ReproducibleTestRunner
> python: disable too-many-positional-arguments warning
> python: silence pylint raising-non-exception error
Thanks, applied to the block branch.
(Yes, of course I had to wait until I ran into the problem patch 2 fixes
myself, and after figuring out the fix from the incomprehensible error
message, I found that this series already contains it.)
Kevin
next prev parent reply other threads:[~2024-11-06 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 17:36 [PATCH 0/4] python: update linting for new mypy/pylint releases John Snow
2024-11-01 17:36 ` [PATCH 1/4] iotests: reflow ReproducibleTestRunner arguments John Snow
2024-11-01 17:36 ` [PATCH 2/4] iotests: correct resultclass type in ReproducibleTestRunner John Snow
2024-11-01 17:36 ` [PATCH 3/4] python: disable too-many-positional-arguments warning John Snow
2024-11-01 17:37 ` [PATCH 4/4] python: silence pylint raising-non-exception error John Snow
2024-11-06 9:57 ` Kevin Wolf [this message]
2024-11-07 16:58 ` [PATCH 0/4] python: update linting for new mypy/pylint releases 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=Zys9g8akOqlpuMQx@redhat.com \
--to=kwolf@redhat.com \
--cc=crosa@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@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).