From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#22137: python-urwid on x86_64: AsyncEventLoopTest Date: Sun, 3 Jan 2016 13:42:07 -0500 Message-ID: <20160103184207.GA29254@jasmine> References: <20151210070556.GA26454@jasmine> <20160101225026.GA14770@jasmine> <8760zavj9s.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38319) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFncP-0004X5-De for bug-guix@gnu.org; Sun, 03 Jan 2016 13:43:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFncM-0002Io-5T for bug-guix@gnu.org; Sun, 03 Jan 2016 13:43:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:48648) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFncM-0002Ik-1f for bug-guix@gnu.org; Sun, 03 Jan 2016 13:43:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aFncL-0002jE-TV for bug-guix@gnu.org; Sun, 03 Jan 2016 13:43:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <8760zavj9s.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 22137@debbugs.gnu.org On Sun, Jan 03, 2016 at 03:18:23PM +0100, Ludovic Courtès wrote: > Leo Famulari skribis: > > > 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. > >> > >> I looked for interesting changes made between the last successful build > >> 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 — previously it had been an > >> external library. [0] Our python-3.4.3 package passes its 'test_asyncio' > >> test, FWIW. > >> > >> 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. > >> > >> 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? > > I think it’s best to avoid introducing version differences. > > 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"? In that case, how about just disabling that test by changing the failing procedure's name, as done in python-pyopenssl? > > Thanks, > Ludo’.