[PKG-Openstack-devel] Bug#743077: python-trollius: FTBFS: Tests failures

[David Suárez]

Source: python-trollius
Version: 0.1.4+20140210+git+6f1f9233b1-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140329 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«BUILDDIR»/python-trollius-0.1.4+20140210+git+6f1f9233b1'
> dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils --with python2,python3
> dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: binary binary-arch binary-indep build build-arch build-indep clean install install-arch install-indep)
> nosetests tests
> ...........................................................SSS..............................................................SSS...................................................SSS....................................................................................................................................................................................................................................................................................................................S.....................................................................................................................................................................................................................................SS
> ----------------------------------------------------------------------
> Ran 721 tests in 21.226s
> 
> OK (SKIP=12)
> nosetests3 tests
> make[1]: nosetests3: Command not found
> make[1]: *** [override_dh_auto_test] Error 127

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/03/29/python-trollius_0.1.4+20140210+git+6f1f9233b1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.