Dear maintainer(s),
With a recent upload of unattended-upgrades the autopkgtest of
unattended-upgrades fails in testing when that autopkgtest is run with
the binary packages of unattended-upgrades from unstable. It passes when
run with only packages from testing. In tabular form:
pass fail
unattended-upgrades from testing 2.13
all others from testing from testing
I copied some of the output at the bottom of this report. A note from
quick inspection: judging from the name I'd say that this test is more
of a *source* quality test and is better used in an upstream ci pipeline
than in an autopkgtest (which is meant to test as-installed binary
properties). I recognize that Debian is upstream from this package, so I
guess a salsa ci pipeline is the better place. E.g. using source linters
is also typically not great in an autopkgtests as they can regress if
the linter gets updated, which shouldn't block the linter from migrating.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
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=unattended-upgrades
https://ci.debian.net/data/autopkgtest/testing/amd64/u/unattended-upgrades/74864537/log.gz
======================================================================
132s FAIL: test_pep484_clean
(test.test_pep484.PackagePep484TestCase.test_pep484_clean)
132s ----------------------------------------------------------------------
132s Traceback (most recent call last):
132s File "/tmp/autopkgtest.vHQfIl/build.K1c/src/test/test_pep484.py",
line 23, in test_pep484_clean
132s self.assertEqual(res, 0)
132s ~~~~~~~~~~~~~~~~^^^^^^^^
132s AssertionError: 2 != 0
132s 132s
----------------------------------------------------------------------
132s Ran 99 tests in 17.138s
132s 132s FAILED (failures=1, skipped=6)
132s autopkgtest [06:39:20]: test run-tests