Package: django-restricted-resource Version: 2014.04-1 User: [email protected] Usertags: autopkgtest
Hello, django-restricted-resource's autopkgtest currently fails [1] with a lot of stderr output. http://ci.debian.net did not yet pick this up, but it will fail there for the same reason. That's easily rectified by adding "Restrictions: allow-stderr" to debian/tests/control, or fixing the test to report progress to stdout (which gives you the added benefit of catching unexpected warnings). But the bigger issue is that this doesn't at all test the installed package but the build tree. The purpose of an autopkgtest is to make sure the *package* works, as tests against the build tree already (should) run during package build. So I advise to not run the upstream test suite again, but instead craft a small "smoke test" from a python script that imports the module (therefore ensuring it's correctly packaged and has correct dependencies) and calling a simple function/method in it. Thanks, Martin [1] https://jenkins.qa.ubuntu.com/job/utopic-adt-django-restricted-resource/ARCH=amd64,label=adt/1/console -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
