On Mon, Jun 15, 2015 at 07:16:03PM +0200, Martin Pitt wrote: > Hello Dominic, > > Dominic Hargreaves [2015-06-15 14:32 +0100]: > > I thought about 'no autodep8', but the semantics aren't quite correct, > > since a package could declare Testsuite: autopkgtest, but rely on the > > autodep8 behaviour. > > Right, that happens all the time with perl/ruby, as Nico and Antonio > pointed out. They (should) have a different Testsuite: header in that > case. > > > So by 'declare tests', I was really talking about having Testsuite: > > autopkgest in the control file. Sorry if that wasn't clear. > > To be honest I'm confused now. So "Testsuite: autopkgtest" -> there > should be "local" tests in debian/tests/control. > "Testsuite: autopkgtest-pkg-perl" -> autodep8 centralized tests. With > the new --no-auto-control you can disable the latter. > > But as said, this field doesn't concern adt-run itself at all -- you > give it a package and it'll run it. It's just a hint to the > higher-layer CI system which decides which tests to run at a time. > > So what's missing/wrong now?
Something to satisfy my original use case where I simply run adt-run against all the packages I'm interested in, and only the ones with 'validated' tests actually run. But it's not too much work to inspect the Testsuite header directly, I suppose, so feel free to consider this request closed - since it sounds like that goes against the design of the package. Disabling the autodep8 tests will be useful too! Thanks! Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
