Dear Maintainer,

It's not clear to me that coverage's own test suite is run during
package build.  I see this in the logs:

   debian/rules override_dh_auto_test
   make[1]: Entering directory /tmp/buildd/python-coverage-3.7+dfsg.1'
   python2.7 setup.py test -vv
   running test
   python3.3 setup.py test -vv
   running test
   make[1]: Leaving directory /tmp/buildd/python-coverage-3.7+dfsg.1'

but the output doesn't give me much confidence that the test suite
actually runs.  I'd expect to see some dots or more verbose
line-by-line output for the tests or... something!

Please verify that the test suite gets run during package build.  For
bonus, can you also look at adding DEP 8 (autopkgtest) tests?


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

Kernel: Linux 3.11-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-coverage depends on:
ii  libc6                 2.17-95
ii  python                2.7.5-5
ii  python-pkg-resources  0.6.49-2

Versions of packages python-coverage recommends:
ii  libjs-jquery              1.7.2+dfsg-3
ii  libjs-jquery-hotkeys      0~20130707+git2d51e3a9+dfsg-2
ii  libjs-jquery-isonscreen   1.2.0-1
ii  libjs-jquery-tablesorter  8-2

python-coverage suggests no packages.

- -- no debconf information
iQIcBAEBCAAGBQJShnruAAoJEBJutWOnSwa/J70QALIWEH2A14/5F2Ngml+Cjb5N
eoARwZjOBTsjI93/uLTyKBQVfBVDQjwiJP2VBQLe8FjOmM0LEWkHWUfuaEPYOq1W
apXAfld0tCIhNMwi3a7sUkgEXd8PqmnuvGmttVByWIpmXowvmulBs/9xxBa9Zqc6
Oc2u2bLZES5Uq1ancE0xtdI8jPAndtQ8p8apZgy91UvANwuEHOq3Ql9X7tO17o9i
gE1PZetsjwen/Pe+f4Z8CVjJCnLt1PF8ASZ/7dQfacF/WnhDZoH5N8ns6QW9xeb6
GKsEn/kdbdFUR30oyLE0sX67/4KqSveX3fvPPYc0fQDFsSC38FhXbje3od000noF
3xQ6g61NuS3U940KDVT2nHuSUz9nB5O88oRsuaXT4QmpxF8SiIZJof1HngmjtxBV
KAIUmxJdzXTzwg+AnC444b166D0BPYn4uaBpyl0gkn/mVdKwzU0B7ivVYUlm5PoR
rhAN8dqtFHhXjV892L/TEFRk4Wqf0Wne7dHUstRU9vDntPa2hzpEAU96sC/ov51r
qVfCLLNEbsz5/fKY1ZVS0H2wHbBQEnZevPNFbv8UHQKEJxJFkQnoNQ36wNeySx+e
a/oOFdBXMSEw1IdGaayjcaxPnRH5QaHdKdWBo1UBKNZJ20Sfm0LDhnE/+V91/+W9
NJ9VQVaw5mXZgtEikeJY
=kk1U
-----END PGP SIGNATURE-----

reassign 729684 src:python-coverage
retitle 729684 Upstream test suite doesn't run during build
tags 729684 + confirmed upstream
thanks

Right, the ‘setup.py test’ command just silently succeeds, without running
any tests.

When trying to *actually* run the unit tests, with ‘python2.7 -m unittest
discover’, the test suite gets a great number of errors, as reported at
<URL:https://bitbucket.org/ned/coveragepy/issue/276/tests-fail-on-osgetcwd>.
That bug report is closed as “INVALID” on the basis that “Tests should be
run with tox.”

However, my attempts to run ‘tox’ in the build environment fail, because
‘tox’ apparently ignores the OS-packaged libraries (e.g. ‘nose’, ‘mock’)
and tries to download them from the internet.

My limited knowledge of ‘tox’ leads me to believe it's not designed to run
under build control in the way we need. So I need to learn whether ‘tox’
can be convinced to run successfully under a package build environment, or
whether that's not feasible.

package src:python-coverage
retitle 729684 src:python-coverage: Upstream test suite doesn't run during build
forwarded 729684 https://bitbucket.org/ned/coveragepy/issue/281/
thanks

I have reported issue #281 in the upstream issue tracker, requesting the
source tarball to include the necessary parts to run the test suite
<URL:https://bitbucket.org/ned/coveragepy/issue/281/>.

The test suite in the upstream source now requires ‘unittest-mixins’,
which is not yet packaged for Debian.

The upstream source now includes the test suite and definitions of how
to run them automatically, so upstream issue #281 is resolved.

Since this bug report was opened, the upstream test suite now has
build dependencies not all of which are packaged in Debian. That
blocks resolution of this bug.

Unblocking - coveragepy removed the use of unittest-mixins in early 2021.