Your message dated Sun, 20 Dec 2020 12:25:36 +0000
with message-id <[email protected]>
and subject line Bug#974460 fixed in goocalendar
has caused the Debian Bug report #974460,
regarding goocalendar: autopkgtest must be marked superficial
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
974460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974460
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: goocalendar
X-Debbugs-CC: [email protected]
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in goocalendar is running a
trivial command that does not provide significant test coverage:
- python3 -c "import goocalendar ; print(goocalendar.__version__)"
Executing that command is considered to be a trivial test, which
does not provide significant coverage for a package as a whole.
But these tests are a useful way to detect regressions in dependencies
and prevent them from breaking your package.
However, it is important that we are realistic about the level of
test coverage provided by these commands: most regressions cannot be
detected in this way. So it is not appropriate for packages with only
superficial tests to have the reduced migration time to migrate from
unstable to testing as that means less opportunity for testing by users
compared to the package with no tests.
To support this, the keyword "Restrictions: superficial" has been
defined [1]. Packages where all tests are marked with this keyword are not
considered for the reduced migration age from unstable to testing, and
will not be allowed to migrate automatically in later stages of the
freeze [2].
Its always better to have more extensive testing than having
superficial testing, which again is better than having no test.
Please consider i) Adding a non-trivial test, and/or ii) Mark the
trivial test with "Restrictions: superficial", similar to
[3] or [4].
The Release Team has listed this issue in the list of Release Critical
Issues for bullseye [5] and has mentioned that the test must be marked
superficial if it is not testing one of its own installed binary
packages in some way. As a result, the severity of this bug report might
be increased to serious in future.
[1]
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#defined-restrictions
[2] https://release.debian.org/bullseye/freeze_policy.html
[3]
https://salsa.debian.org/utopia-team/dbus/-/commit/a80908df7d119b181eec5eb0542634a30c2ad468
[4]
https://salsa.debian.org/apparmor-team/apparmor/-/commit/580667513a097088ebe579884b38ac8d8666d3b3
[5] https://release.debian.org/bullseye/rc_policy.txt
--
Regards
Sudip
--- End Message ---
--- Begin Message ---
Hello,
Bug #974460 in goocalendar reported by you has been fixed in the Git repository.
You can see the commit message below and you can check the diff of the fix at:
https://salsa.debian.org/tryton-team/goocalendar/-/commit/42c394439a75c22f182a136ee9ff83dab52c1e41
------------------------------------------------------------------------
Mark the autopkgtest as superficial (Closes: #974460).
------------------------------------------------------------------------
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/974460
--- End Message ---
