On Tue, Jan 11, 2022 at 10:22:44PM +0100, Paul Gevers wrote: > Source: mypy, python-sop > Control: found -1 mypy/0.931-1 > Control: found -1 python-sop/0.2.0-1.1 > Severity: serious > Tags: sid bookworm > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: breaks needs-update > > Dear maintainer(s), > > With a recent upload of mypy the autopkgtest of python-sop fails in testing > when that autopkgtest is run with the binary packages of mypy from unstable. > It passes when run with only packages from testing. In tabular form: > > pass fail > mypy from testing 0.931-1 > python-sop from testing 0.2.0-1.1 > all others from testing from testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration of mypy to testing [1]. > Due to the nature of this issue, I filed this bug report against both > packages. Can you please investigate the situation and reassign the bug to > the right package? > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=mypy > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-sop/18224287/log.gz > > sop/__init__.py:224: error: Missing type parameters for generic type > "_SubParsersAction" > sop/__init__.py:387: error: Missing type parameters for generic type > "_SubParsersAction" > Found 2 errors in 1 file (checked 3 source files) > autopkgtest [21:22:47]: test command2
Running static analysis tools such as mypy as part of autopkgtest, or even as build time tests, is an anti-pattern. New versions of the tools tend to always find new issues but they usually have no impact on the runtime behavior of the package. I understand it's useful to have this type of checks against the source, but I suggest you do that on salsa CI instead since there it won't affect the tools themselves.
signature.asc
Description: PGP signature
