Graham Inggs: > Package: release.debian.org > Severity: wishlist > > Dear Release Team > > I recall some discussion from dc16 and I see a talk planned for dc17 > [1] on using autopkgtest results for unstable to testing migration. > In other words, package uploads that cause autopkgtests to fail, where > those tests passed previously, should be prevented from migrating to > testing. The regression can be in the uploaded package's own > autopkgtests, or in those of a reverse dependency. > > Can a decision please be made, as to whether autopkgtest regressions > will be considered RC for buster, so that bugs of severity level > 'serious' can be filed now? > > Regards > Graham > > > [1] https://debconf17.debconf.org/talks/2/ >
Hi Graham, Thanks for the interest in getting this clarified. I am not sure yet whether it will be ready for buster, but I think we can defer this to a later time (a la 6 months to a year). The status quo is that: * A failure can be RC if it basically shows that the package is broken or have significantly regressed in functionality (possibly caused by a dependency). * But autopkgtests failures in themselves are not RC at the moment. Related: The idea presented in the DebConf17 talk is by no means new. This already thought up and agreed upon during DC13 plus announced on d-d-a back then. What changed is that Paul Gevers volunteered to do it (much appreciated, btw.). If you would like to help make this move forward then you are welcome to: * Assist Paul with implementing the necessary feature set in ci.d.n and Britney. * Analyse autopkgtests failures and file bugs as appropriate (RC when the package appears to be actually broken, non-RC otherwise). - Patches are probably very welcome here as well. Thanks, ~Niels
