Bug#983233: New autopkgtest shouldn’t trigger a regression
Le 21/02/2021 à 16:02, Paul Gevers a écrit : Control: tags -1 moreinfo Hi David, On 21-02-2021 12:53, David Prévot wrote: I recently added an autopkgtest to a package, and the autopkgtest failed on all suites. I’m surprised to see that failure considered as a regression (#983211) […] We realize that `regression` doesn't quite cover how we use it […] we consider failing tests in testing RC [1]. Hence, allowing a package with a failing test to migrate to testing would immediately make it RC buggy, hence we block it. `regression` doesn't fully cover it, we read it as "there wasn't an RC bug in testing, and now there will be, hence regression" but it's a bit stretched. Do you have a suggestion to use there instead (a word, not a sentence)? Maybe “failing test” since you used it twice to describe the actual issue (but that’s two words) or even simply (test) “failure”? The current policy makes it almost worth to remove autopkgtest in order to avoid what you call “regression”. Yet, such removal would check all boxes of what is called “regression” according to some some online [dict]ionary: “a return to a previous and less advanced or worse state, condition, or way of behaving”. dict: https://dictionary.cambridge.org/dictionary/english/regression Regards David
Processed: Re: Bug#983233: New autopkgtest shouldn’t trigger a regression
Processing control commands: > tags -1 moreinfo Bug #983233 [release.debian.org] New autopkgtest shouldn’t trigger a regression Added tag(s) moreinfo. -- 983233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983233: New autopkgtest shouldn’t trigger a regression
Control: tags -1 moreinfo Hi David, On 21-02-2021 12:53, David Prévot wrote: > I recently added an autopkgtest to a package, and the autopkgtest failed > on all suites. I’m surprised to see that failure considered as a > regression (#983211), so I believe there is a mistake somewhere (maybe > that’s just me not getting what “regression” means, if so that might > deserve being documented). We realize that `regression` doesn't quite cover how we use it in Debian, but this part was taken over from Ubuntu. In Debian, we consider failing tests in testing RC [1]. Hence, allowing a package with a failing test to migrate to testing would immediately make it RC buggy, hence we block it. `regression` doesn't fully cover it, we read it as "there wasn't an RC bug in testing, and now there will be, hence regression" but it's a bit stretched. Do you have a suggestion to use there instead (a word, not a sentence)? Paul [1] https://release.debian.org/bullseye/rc_policy.txt OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#983233: New autopkgtest shouldn’t trigger a regression
Processing control commands: > reassign -1 release.debian.org Bug #983233 [debci] New autopkgtest shouldn’t trigger a regression Bug reassigned from package 'debci' to 'release.debian.org'. Ignoring request to alter found versions of bug #983233 to the same values previously set Ignoring request to alter fixed versions of bug #983233 to the same values previously set -- 983233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983233: New autopkgtest shouldn’t trigger a regression
Package: debci Severity: normal X-Debbugs-Cc: Debian Release Team Hi, I recently added an autopkgtest to a package, and the autopkgtest failed on all suites. I’m surprised to see that failure considered as a regression (#983211), so I believe there is a mistake somewhere (maybe that’s just me not getting what “regression” means, if so that might deserve being documented). Regards David signature.asc Description: PGP signature
