[Python-modules-team] Bug#917677: python-django-push-notifications: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.7 --system=custom "--test-args={interpreter} tests/runtests.py" returned exit code 13

[Lucas Nussbaum]

Source: python-django-push-notifications
Version: 1.4.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_test -- --system=custom --test-args="{interpreter} tests/runtests.py"
> I: pybuild base:217: python3.7 tests/runtests.py
> F...............................
> ======================================================================
> FAIL: test_validation (test_rest_framework.APNSDeviceSerializerTestCase)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/<<PKGBUILDDIR>>/tests/test_rest_framework.py", line 48, in test_validation
>     self.assertEqual(serializer.errors["device_id"][0], '"ffffffffffffffffffffffffffffake" is not a valid UUID.')
> AssertionError: ErrorDetail(string='Must be a valid UUID.', code='invalid') != '"ffffffffffffffffffffffffffffake" is not a valid UUID.'
> 
> ----------------------------------------------------------------------
> Ran 32 tests in 0.050s
> 
> FAILED (failures=1)
> Creating test database for alias 'default'...
> deactivating [616263]
> deactivated 1 devices
> E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: python3.7 tests/runtests.py
> dh_auto_test: pybuild --test -i python{version} -p 3.7 --system=custom "--test-args={interpreter} tests/runtests.py" returned exit code 13

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/python-django-push-notifications_1.4.1-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.