[Debian-med-packaging] Bug#839346: python-pbcore: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-pbcore
Version: 1.2.9+dfsg-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20160930 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):
> Traceback (most recent call last):
>   File "/<<BUILDDIR>>/python-pbcore-1.2.9+dfsg/tests/test_pbdataset_subtypes.py", line 71, in test_valid_referencesets
>     validateXml(ET.parse(data.getXml(9)).getroot(), skipResources=True)
>   File "/<<BUILDDIR>>/python-pbcore-1.2.9+dfsg/pbcore/io/dataset/DataSetValidator.py", line 63, in validateXml
>     from pbcore.io.dataset import DataSetXsd
>   File "/<<BUILDDIR>>/python-pbcore-1.2.9+dfsg/pbcore/io/dataset/DataSetXsd.py", line 24, in <module>
>     raise pyxb.PyXBVersionError(_PyXBVersion)
> PyXBVersionError: 1.2.4
> 
> ----------------------------------------------------------------------
> Ran 293 tests in 25.785s
> 
> FAILED (errors=10, skipped=28)
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: python2.7 setup.py test
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13
> debian/rules:32: recipe for target 'override_dh_auto_test' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

The full build log is available from:
   http://aws-logs.debian.net/2016/09/30/python-pbcore_1.2.9+dfsg-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.