Package: autopkgtest
Version: 2.7

I have a package which has one test with breaks-testbed restriction, and no other test. This is what happens when I try to run the tests against virt-server that doesn't support this restriction:

# sudo adt-run -B adequate-0.11.4// --- adt-virt-null
adt-run: $ vserver: adt-virt-null
adt-run: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ builds ...
adt-run: @@@@@@@@@@@@@@@@@@@@ ubtree ubtree0
adt-run: $ ubtree0-extract: sh -ec <SCRIPT> x 
/tmp/adt-run.4JfFHd/ubtree0-build/tmpdir /tmp/adt-run.4JfFHd/ubtree0-build/real-tree
dpkg-source: info: using options from 
/tmp/adt-run.4JfFHd/ubtree0-build/real-tree/debian/source/options: 
--compression=gzip
adequate             SKIP Test breaks testbed but testbed does not advertise 
revert-full-system
adt-run: * <ubtree:ubtree0> build not needed
adt-run: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ builds done.
adt-run: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests ...
adt-run: @@@@@@@@@@@@@@@@@@@@ test ubtree ubtree0
adequate             SKIP Test breaks testbed but testbed does not advertise 
revert-full-system
adt-run: @@@@@@@@@@ run_tests ...
*                    SKIP package has metadata but no tests
adt-run: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ tests done.


The “package has metadata but no tests” message is misleading. The package certainly does have tests, it's just all of them were skipped. Additionally, the exit status is 10, which is not one of the codes documented in the manual page:

# echo $?
10


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages autopkgtest depends on:
ii  apt-utils      0.9.15
ii  debhelper      9.20131227
ii  pbuilder       0.215
ii  python         2.7.5-5
ii  python-debian  0.1.21+nmu3

--
Jakub Wilk


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to