Your message dated Thu, 29 Jan 2026 18:34:21 +0100
with message-id <[email protected]>
and subject line Re: britney: triggers tests even when all tests are removed;
potentially causing autodep8 to be called
has caused the Debian Bug report #939982,
regarding britney: triggers tests even when all tests are removed; potentially
causing autodep8 to be called
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.)
--
939982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939982
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
User: [email protected]
Usertags: britney
Hi Eriberto,
Thanks for talking about the issues you have, I could not have guessed.
On 10-09-2019 17:53, Eriberto Mota wrote:
> I was using a test over a DKMS package (lime-forensics). I removed
> all tests[1] because Debian wasn't process it (adding a Neutral tag)
> and to close the bug #935543. Now I have a regression in my
> package[2][3]. However, I no longer maintain a test. I think it is a
> bug in debci. How to proceed to avoid a regression after removing all
> tests?
This is not an issue with debci, as that just runs tests on behalf of
other entities. The culprit here is britney, the migration software of
the release team, hence filing a bug against it. The problem is that the
migration software *seems* (I haven't checked properly yet) to trigger
even in the case that all tests are removed. Because autopkgtest (the
software) is by default configured to try and call autodep8 if no tests
are found, you package was tested with tests from autodep8, while in
your case that is inappropriate as they fail. You have no way of telling
the infrastructure that. As britney considering neutral-to-fail a
regression your package is flagged as such. I see that's nothing you can
solve so I'll ignore the failure.
> [1]
> https://salsa.debian.org/pkg-security-team/lime-forensics/commit/d7d4c79ae7ea55c5d64cc6103d3745e199056284
> [2] https://ci.debian.net/packages/l/lime-forensics/
> [3]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939893
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi,
On Tue, 10 Sep 2019 20:42:56 +0200 Paul Gevers <[email protected]> wrote:
The problem is that the
migration software *seems* (I haven't checked properly yet) to trigger
even in the case that all tests are removed.
I just checked the code, I don't think it's doing this (anymore), the
code explicitly checks the source suite. Hence closing.
https://salsa.debian.org/release-team/britney2/-/blob/6532e1c0a27eefb3e8b2b5b283ef921c3e3ea70a/britney2/policies/autopkgtest.py#L1170
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
