reassign 729684 src:python-coverage retitle 729684 Upstream test suite doesn't run during build tags 729684 + confirmed upstream thanks
On 15-Nov-2013, Barry Warsaw wrote: > Please verify that the test suite gets run during package build. 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. -- \ “If I had known what it would be like to have it all... I might | `\ have been willing to settle for less.” —Jane Wagner, via Lily | _o__) Tomlin | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
