[Python-modules-team] Bug#854496: python-qtpy: FTBFS randomly (failing tests)

[Ghislain Vaillant]

On Mon, 2017-02-13 at 19:42 +0100, Santiago Vila wrote:
> > As far as this bug is concerned, all I can do is tag it for help, since
> > I have no clue how to make any sort of progress. If yourself or someone
> > else finds a fix for it, I will happily incorporate the corresponding
> > patches.
> 
> A closer look tells me that this is not really random.
> 
> Instead, it always fails on the fast machines I have, and never on the
> slower ones. When it fails, we can see this in the build log:
> 
> tests/test_uic.py Aborted
> 
> so I tried "ulimit -c unlimited" before "dpkg-buildpackage -uc -us -b"
> and this was the result:
> 
> https://people.debian.org/~sanvila/python-qtpy/python-qtpy-1.2.1.build.tar.gz
> 
> This is the whole build tree, including the "core" file that was generated
> by the python interpreter, so in addition to the help tag, I would also:
> 
> a) disable tests/test_uic.py until further notice, as we don't know
> why it fails.

Well, it sounds like an environment related issue. The fact that it
builds correctly both on the builders and locally, and tests fine on
both debci (which runs the very same test suite) and upstream travis
hints me towards this conclusion.

Also, looking at the current logs in reproducible builds, the execution
of the tests is aborted (timeout?), not marked as FAILED, which is a
sign that the failure of the tests is triggered by something external.

Actually, the termination of the tests does not systematically happen
at `tests/test_uic.py` (at `tests/test_patch_qheaderview.py` on amd64,
at `tests/test_patch_qcombobox.py` on arm64). So, the solution you
proposed would not solve what is happening on reproducible builds.

> b) forward the bug upstream so that the author investigates about it.

Done. Upstream is clueless, unsurprisingly.