autopkgtest test suites are not automatically run against SRU uploads

[Robie Basak]

https://wiki.ubuntu.com/ProposedMigration running autopkgtest test suites have proved particularly useful for the development release. SRUs are particularly regression sensitive, and as we increase our autopkgtest coverage, we should also run these tests (and those of all reverse dependencies) before promoting an SRU, but this is currently not done.

11:03 <rbasak> pitti: do we have a bug on dep8 tests not run on SRUs?
11:04 <rbasak> I have a case where I want this as part of a wider effort, so want something to refer to current status of it.
11:04 <pitti> rbasak: ah, we can run them manually if desired, but we don't run britney on stables
11:04 <pitti> rbasak: perhaps we should though, even for SRUs
11:05 <rbasak> pitti: we want to do this though, right?
11:05 <rbasak> pitti: can I file a bug to track this, and if so, what should it be filed against?
11:05 <pitti> it would certainly be another nice barrier to avoid publishing broken stuff
11:06 <pitti> rbasak: hmm, good question -- https://bugs.launchpad.net/britney isn't configured
11:06 <pitti> rbasak: so perhaps just "ubuntu" with subscribing the release team?
11:06 <rbasak> pitti: ack. Thanks!

[Martin Pitt (pitti)]

So it would be nice to run britney in a "no-act" mode on stable-proposed, so that it shows when a package is a valid candidate and the reverse depends tests status, but does not actually promote it to -updates (as we want to do that manually). Would that be feasible?

[Colin Watson (cjwatson)]

Should be. I've recently done some of the generalisation work on proposed-migration to make this feasible. Hopefully I can push this the rest of the way up the hill soon ...

[Colin Watson (cjwatson)]

This is now done on trusty and utopic. precise remains (blocked on https://code.launchpad.net/~cjwatson/britney/dynamic-arches/+merge/250462).

[Iain Lane (laney)]

I think this is done now.