[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#898014: marked as done (autopkgtest-pkg-python in Testsuite ignored if tests/control exists)

Your message dated Sun, 6 May 2018 06:34:14 +0200
with message-id <11f03468-545c-167a-e382-d0584360ee68@debian.org>
and subject line Re: Bug#898014: autopkgtest-pkg-python in Testsuite ignored if tests/control exists
has caused the Debian Bug report #898014,
regarding autopkgtest-pkg-python in Testsuite ignored if tests/control exists
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
898014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898014
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: autopkgtest
Version: 5.3.1
Severity: wishlist

I have a package (remctl) that provides both Perl and Python bindings with
corresonding binary packages.  I want to run autopkgtest-pkg-perl and
autopkgtest-pkg-python tests on the corresponding binary packages.

autodep8 can't see how to run Perl tests because the Perl module is in a
perl subdirectory, which isn't surprising, so just adding
autopkgtest-pkg-perl to the Testsuite control field didn't work for those
tests.  I therefore manually created a debian/tests/control file with the
corresponding content, and that works fine (except for the smoke tests
because of the subdirectory thing, but I can work on that later).

Surprisingly, once I did that, the autopkgtest-pkg-python tests specified
via the Testsuite control field stopped running.  That value was ignored
once a debian/tests/control file exists.

In retrospect, this makes sense given what I suspect to be the implementation
using autodep8, but it's unfortunate.  If I explicitly list
autopkgtest-pkg-python in Testsuite, it would be nice to still generate and
run a test control file using autodep8 for it as well as the
manually-specified debian/tests/control file.  (In other words, I would
like to run the merger of the tests in debian/tests/control plus the tests
corresponding to any autopkgtest-pkg-* entries in the Testsuite control
field.)

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages autopkgtest depends on:
ii  apt-utils       1.6.1
ii  libdpkg-perl    1.19.0.5
ii  procps          2:3.3.14-1+b1
ii  python3         3.6.5-3
ii  python3-debian  0.1.32

Versions of packages autopkgtest recommends:
ii  autodep8  0.12

Versions of packages autopkgtest suggests:
pn  lxc          <none>
pn  lxd-client   <none>
pn  qemu-system  <none>
pn  qemu-utils   <none>
ii  schroot      1.6.10-4

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi Russ,

On 05-05-18 23:55, Russ Allbery wrote:
In other words, I would
> like to run the merger of the tests in debian/tests/control plus the tests
> corresponding to any autopkgtest-pkg-* entries in the Testsuite control
> field.

Rename debian/tests/control to debian/tests/control.autodep8 and you get
what you want as documented $(man autodep8).

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: