From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#22137: python-urwid on x86_64: AsyncEventLoopTest Date: Mon, 04 Jan 2016 00:02:09 +0100 Message-ID: <878u46qnbi.fsf@gnu.org> References: <20151210070556.GA26454@jasmine> <20160101225026.GA14770@jasmine> <8760zavj9s.fsf@gnu.org> <20160103184207.GA29254@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFrg2-0003M0-DO for bug-guix@gnu.org; Sun, 03 Jan 2016 18:03:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFrfy-0002OT-4J for bug-guix@gnu.org; Sun, 03 Jan 2016 18:03:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:48745) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFrfy-0002OP-0s for bug-guix@gnu.org; Sun, 03 Jan 2016 18:03:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aFrfx-0000OC-Oj for bug-guix@gnu.org; Sun, 03 Jan 2016 18:03:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20160103184207.GA29254@jasmine> (Leo Famulari's message of "Sun, 3 Jan 2016 13:42:07 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Leo Famulari Cc: 22137@debbugs.gnu.org Leo Famulari skribis: > On Sun, Jan 03, 2016 at 03:18:23PM +0100, Ludovic Court=C3=A8s wrote: >> Leo Famulari skribis: >>=20 >> > On Thu, Dec 10, 2015 at 02:05:56AM -0500, Leo Famulari wrote: >> >> python-urwid-1.3.0 fails to build on x86_64 during the >> >> "AsyncioEventLoopTest" test with the error "KeyError: '5 is not >> >> registered'". It has failed repeatedly for some time now. It fails in >> >> the same way when updated to python-urwid-1.3.1. >> >>=20 >> >> I looked for interesting changes made between the last successful bui= ld >> >> and the first failing build. Notably, this range includes the upgrade >> >> from python-3.3.5 to python-3.4.3 (08c04509). Asyncio was integrated >> >> into the Python standard library in 3.4 =E2=80=94 previously it had b= een an >> >> external library. [0] Our python-3.4.3 package passes its 'test_async= io' >> >> test, FWIW. >> >>=20 >> >> I entered the failed build tree and successfully ran the tests using = the >> >> python-3.4.3-7 [1] installed by Debian Stretch. That only tells us so >> >> much, but I think it does indicate either a bug in our python-3.4.3, = or >> >> some problem with python-urwid caused by the unfamiliar Guix build >> >> environment. >> >>=20 >> >> Here's the hydra.gnu.org page: >> >> http://hydra.gnu.org/build/861615 >> > >> > BTW, I filed a bug upstream: >> > https://github.com/urwid/urwid/issues/164 >> > >> > No response yet, although I should add some more information to the bug >> > report. >> > >> > In the meantime, what about downgrading python-urwid to 1.2.2 and >> > leaving python2-urwid at 1.3.0? >>=20 >> I think it=E2=80=99s best to avoid introducing version differences. >>=20 >> What about disabling tests in python2-urwid in the meantime, with a >> comment pointing to the above bug report? > > I assume you mean "disabling tests in python-urwid"? Yes, sorry. > In that case, how about just disabling that test by changing the failing > procedure's name, as done in python-pyopenssl? Sure, that=E2=80=99s even better. Ludo=E2=80=99.