Bug#839253: autopkgtest: --testname incompatible with Test-Command:

2016-12-01 Thread Martin Pitt
Hello Barry, Ian, Ian Jackson [2016-10-23 17:21 +0100]: > I see in fact that is is still not compatible. How about: > > Test-Command: tox -e qa > Depends: @builddeps@, git > Features: test-name=qa That seems okay to me. It would be our first-ever supported "Features:" item, too :-)

Bug#839253: autopkgtest: --testname incompatible with Test-Command:

2016-10-23 Thread Ian Jackson
Ian Jackson writes ("Re: Bug#839253: autopkgtest: --testname incompatible with Test-Command:"): > Barry's suggestion of a Test-Name field is better. This is because if > a package provides > Test-Command-foobar: > it won't be compatibile with software compatible with the

Bug#839253: autopkgtest: --testname incompatible with Test-Command:

2016-10-23 Thread Ian Jackson
Martin Pitt writes ("Bug#839253: autopkgtest: --testname incompatible with Test-Command:"): > Hey Barry, > > * Add a Test-Name: field solely for the purpose of matching > > --testname. Of course if Test-Name doesn't exist, it would fall > > back to matching on

Bug#839253: autopkgtest: --testname incompatible with Test-Command:

2016-09-30 Thread Barry Warsaw
On Oct 01, 2016, at 12:16 AM, Martin Pitt wrote: >You can actually -- they get named "command1", "command2", etc, same >names that appear in the logs and in summary. I must have missed that, but it's really nice. pgpIUkqcn_THD.pgp Description: OpenPGP digital signature

Bug#839253: autopkgtest: --testname incompatible with Test-Command:

2016-09-30 Thread Barry Warsaw
On Oct 01, 2016, at 12:16 AM, Martin Pitt wrote: >I'd slightly change that idea to be Test-Command-foobar:, to provide >an optional name? Test-Command: would then continue to get >autogenerated commandN names. I rather like that. One of my other minor problems is that in the summary, if you

Bug#839253: autopkgtest: --testname incompatible with Test-Command:

2016-09-30 Thread Martin Pitt
Hey Barry, Barry Warsaw [2016-09-30 14:17 -0400]: > AFAICT, if you specify a test with Test-Command: there's no way to > select it with `autopkgtest --testname`. A couple of thoughts: You can actually -- they get named "command1", "command2", etc, same names that appear in the logs and in

Bug#839253: autopkgtest: --testname incompatible with Test-Command:

2016-09-30 Thread Barry Warsaw
Package: autopkgtest Version: 4.0.5 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, AFAICT, if you specify a test with Test-Command: there's no way to select it with `autopkgtest --testname`. A couple of thoughts: * Allow Tests: and Test-Command: to