[Python-modules-team] Bug#844139: python-django: FTBFS: Tests failures

[Lucas Nussbaum]

Source: python-django
Version: 1:1.10.3-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20161111 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):
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> Destroying test database for alias 'other' (':memory:')...
> debian/rules:24: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/11/11/python-django_1.10.3-1_unstable.log

This failure happens on a CPU with TSX extensions available, but is not
reproducible on a machine without them. For context, I recommend reading the
thread starting at https://lists.debian.org/debian-devel/2016/11/msg00210.html

The node used is an Amazon EC2 VM with 64 cores. /proc/cpuinfo says:
   model    : 79
   model name : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
   stepping : 1

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.