[Python-modules-team] Bug#743118: urwid: FTBFS: Tests failures

[David Suárez]

Source: urwid
Version: 1.2.0-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):
> test3byte (urwid.tests.test_str_util.DecodeOneTest) ... ok
> test4byte (urwid.tests.test_str_util.DecodeOneTest) ... ok
> test_create (urwid.tests.test_decoration.FillerTest) ... ok
> test_repr (urwid.tests.test_decoration.FillerTest) ... ok
> test_values (urwid.tests.test_decoration.FillerTest) ... ok
> test_create (urwid.tests.test_decoration.PaddingTest) ... ok
> test_cursor (urwid.tests.test_decoration.PaddingTest) ... ok
> test_reduced_padding_cursor (urwid.tests.test_decoration.PaddingTest) ... ok
> test_values (urwid.tests.test_decoration.PaddingTest) ... ok
> 
> ======================================================================
> FAIL: test_run (urwid.tests.test_event_loops.TwistedEventLoopTest)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/«PKGBUILDDIR»/urwid/tests/test_event_loops.py", line 128, in test_run
>     "clean exit"])
> AssertionError: Lists differ: [u'da', u'ta', 'waiting', 'hel... != ['da', 'ta', 'waiting', 'hello...
> 
> First differing element 4:
> clean exit
> waiting
> 
> - [u'da', u'ta', 'waiting', 'hello', 'clean exit', 'waiting']
> + ['da', 'ta', 'waiting', 'hello', 'waiting', 'clean exit']
> 
> ----------------------------------------------------------------------
> Ran 289 tests in 0.862s
> 
> FAILED (failures=1)
> make: *** [build-docs-test-stamp] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/03/29/urwid_1.2.0-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.