From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 22137@debbugs.gnu.org
Subject: bug#22137: python-urwid on x86_64: AsyncEventLoopTest
Date: Sun, 03 Jan 2016 15:18:23 +0100 [thread overview]
Message-ID: <8760zavj9s.fsf@gnu.org> (raw)
In-Reply-To: <20160101225026.GA14770@jasmine> (Leo Famulari's message of "Fri, 1 Jan 2016 17:50:26 -0500")
Leo Famulari <leo@famulari.name> 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?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-01-03 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 7:05 bug#22137: python-urwid on x86_64: AsyncEventLoopTest Leo Famulari
2015-12-10 7:10 ` Leo Famulari
2016-01-01 22:50 ` Leo Famulari
2016-01-03 14:18 ` Ludovic Courtès [this message]
2016-01-03 18:42 ` Leo Famulari
2016-01-03 23:02 ` Ludovic Courtès
2017-08-31 13:28 ` bug#22137: Status: " Maxim Cournoyer
2018-06-12 12:54 ` 宋文武
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760zavj9s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22137@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).