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