GNU bug report logs - #22137
python-urwid on x86_64: AsyncEventLoopTest

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22137 in the body.
You can then email your comments to 22137 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: bug-guix <at> gnu.org
Subject: python-urwid on x86_64: AsyncEventLoopTest
Date: Thu, 10 Dec 2015 02:05:56 -0500

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

Here's the failing part of the build log:

--8<---------------cut here---------------start------------->8---

======================================================================
ERROR: test_remove_watch_file (urwid.tests.test_event_loops.AsyncioEventLoopTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/asyncio/selector_events.py", line 234, in add_reader
    key = self._selector.get_key(fd)
  File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/selectors.py", line 182, in get_key
    raise KeyError("{!r} is not registered".format(fileobj)) from None
KeyError: '5 is not registered'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/nix-build-python-urwid-1.3.0.drv-0/urwid-1.3.0/build/lib.linux-x86_64-3.4/urwid/tests/test_event_loops.py", line 33, in test_remove_watch_file
    handle = evl.watch_file(5, lambda: None)
  File "/tmp/nix-build-python-urwid-1.3.0.drv-0/urwid-1.3.0/build/lib.linux-x86_64-3.4/urwid/main_loop.py", line 1263, in watch_file
    self._loop.add_reader(fd, callback)
  File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/asyncio/selector_events.py", line 237, in add_reader
    (handle, None))
  File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/selectors.py", line 402, in register
    self._epoll.register(key.fd, epoll_events)
PermissionError: [Errno 1] Operation not permitted

----------------------------------------------------------------------
Ran 284 tests in 0.384s

FAILED (errors=1)
phase `check' failed after 4.6 seconds
--8<---------------cut here---------------end--------------->8---

[0]
https://docs.python.org/3/library/asyncio.html

[1] Reported by `apt-cache show python3`, this python-3.4.3-7's .deb has
a SHA256 hash of:
53fa197ee35501152b1897bf84ab6123f7f65201efdddc2e4aa882de494f3870

Message #8 received at 22137 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: 22137 <at> debbugs.gnu.org
Subject: Re: bug#22137: python-urwid on x86_64: AsyncEventLoopTest
Date: Thu, 10 Dec 2015 02:10:49 -0500

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.

Regarding the build environment, I meant add to Nix disables the tests
for their equivalent package.

> 
> Here's the hydra.gnu.org page:
> http://hydra.gnu.org/build/861615
> 
> Here's the failing part of the build log:
> 
> --8<---------------cut here---------------start------------->8---
> 
> ======================================================================
> ERROR: test_remove_watch_file (urwid.tests.test_event_loops.AsyncioEventLoopTest)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/asyncio/selector_events.py", line 234, in add_reader
>     key = self._selector.get_key(fd)
>   File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/selectors.py", line 182, in get_key
>     raise KeyError("{!r} is not registered".format(fileobj)) from None
> KeyError: '5 is not registered'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/tmp/nix-build-python-urwid-1.3.0.drv-0/urwid-1.3.0/build/lib.linux-x86_64-3.4/urwid/tests/test_event_loops.py", line 33, in test_remove_watch_file
>     handle = evl.watch_file(5, lambda: None)
>   File "/tmp/nix-build-python-urwid-1.3.0.drv-0/urwid-1.3.0/build/lib.linux-x86_64-3.4/urwid/main_loop.py", line 1263, in watch_file
>     self._loop.add_reader(fd, callback)
>   File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/asyncio/selector_events.py", line 237, in add_reader
>     (handle, None))
>   File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/selectors.py", line 402, in register
>     self._epoll.register(key.fd, epoll_events)
> PermissionError: [Errno 1] Operation not permitted
> 
> ----------------------------------------------------------------------
> Ran 284 tests in 0.384s
> 
> FAILED (errors=1)
> phase `check' failed after 4.6 seconds
> --8<---------------cut here---------------end--------------->8---
> 
> [0]
> https://docs.python.org/3/library/asyncio.html
> 
> [1] Reported by `apt-cache show python3`, this python-3.4.3-7's .deb has
> a SHA256 hash of:
> 53fa197ee35501152b1897bf84ab6123f7f65201efdddc2e4aa882de494f3870
> 
> 
> 

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: bug-guix <at> gnu.org
Subject: Re: python-urwid on x86_64: AsyncEventLoopTest
Date: Fri, 1 Jan 2016 17:50:26 -0500

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?

1.2.2 works for the software I am trying to package, and currently there
are no users of python-urwid.

> 
> Here's the failing part of the build log:
> 
> --8<---------------cut here---------------start------------->8---
> 
> ======================================================================
> ERROR: test_remove_watch_file (urwid.tests.test_event_loops.AsyncioEventLoopTest)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/asyncio/selector_events.py", line 234, in add_reader
>     key = self._selector.get_key(fd)
>   File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/selectors.py", line 182, in get_key
>     raise KeyError("{!r} is not registered".format(fileobj)) from None
> KeyError: '5 is not registered'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/tmp/nix-build-python-urwid-1.3.0.drv-0/urwid-1.3.0/build/lib.linux-x86_64-3.4/urwid/tests/test_event_loops.py", line 33, in test_remove_watch_file
>     handle = evl.watch_file(5, lambda: None)
>   File "/tmp/nix-build-python-urwid-1.3.0.drv-0/urwid-1.3.0/build/lib.linux-x86_64-3.4/urwid/main_loop.py", line 1263, in watch_file
>     self._loop.add_reader(fd, callback)
>   File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/asyncio/selector_events.py", line 237, in add_reader
>     (handle, None))
>   File "/gnu/store/13n8xbi9wv9pigfyhir007qadr81jq46-python-3.4.3/lib/python3.4/selectors.py", line 402, in register
>     self._epoll.register(key.fd, epoll_events)
> PermissionError: [Errno 1] Operation not permitted
> 
> ----------------------------------------------------------------------
> Ran 284 tests in 0.384s
> 
> FAILED (errors=1)
> phase `check' failed after 4.6 seconds
> --8<---------------cut here---------------end--------------->8---
> 
> [0]
> https://docs.python.org/3/library/asyncio.html
> 
> [1] Reported by `apt-cache show python3`, this python-3.4.3-7's .deb has
> a SHA256 hash of:
> 53fa197ee35501152b1897bf84ab6123f7f65201efdddc2e4aa882de494f3870

Message #14 received at 22137 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Leo Famulari <leo <at> famulari.name>
Cc: 22137 <at> debbugs.gnu.org
Subject: Re: bug#22137: python-urwid on x86_64: AsyncEventLoopTest
Date: Sun, 03 Jan 2016 15:18:23 +0100

Leo Famulari <leo <at> 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’.

Message #17 received at 22137 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 22137 <at> debbugs.gnu.org
Subject: Re: bug#22137: python-urwid on x86_64: AsyncEventLoopTest
Date: Sun, 3 Jan 2016 13:42:07 -0500

On Sun, Jan 03, 2016 at 03:18:23PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo <at> 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?

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’.

Message #20 received at 22137 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Leo Famulari <leo <at> famulari.name>
Cc: 22137 <at> debbugs.gnu.org
Subject: Re: bug#22137: python-urwid on x86_64: AsyncEventLoopTest
Date: Mon, 04 Jan 2016 00:02:09 +0100

Leo Famulari <leo <at> famulari.name> skribis:

> On Sun, Jan 03, 2016 at 03:18:23PM +0100, Ludovic Courtès wrote:
>> Leo Famulari <leo <at> 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?
>
> 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’s even better.

Ludo’.

Message #23 received at 22137 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: bug#22137 <22137 <at> debbugs.gnu.org>
Subject: Re: Status: python-urwid on x86_64: AsyncEventLoopTest
Date: Thu, 31 Aug 2017 09:28:57 -0400

This bug was supposedly fixed upstream [0] but there is no new release
yet. To be revisited after urwid 1.3.2 is released.

[0]: https://github.com/urwid/urwid/issues/164

Message #30 received at 22137-done <at> debbugs.gnu.org (full text, mbox):

From: iyzsong <at> member.fsf.org (宋文武)
To: bug#22137 <22137-done <at> debbugs.gnu.org>
Subject: Re: bug#22137: Status: python-urwid on x86_64: AsyncEventLoopTest
Date: Tue, 12 Jun 2018 20:54:08 +0800

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> This bug was supposedly fixed upstream [0] but there is no new release
> yet. To be revisited after urwid 1.3.2 is released.
>
> [0]: https://github.com/urwid/urwid/issues/164

Hello, I update our urwid to version 2.0.1.

Closing now, thanks!

Message #39 received at 22137 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: 22137 <at> debbugs.gnu.org
Subject: A test of bug #44996
Date: Wed, 12 Mar 2025 19:25:10 -0400

I've unarchived and reopened this bug in order to test another bug in
our issues tracker:

https://issues.guix.gnu.org/44996

Sorry for the noise...

Message #44 received at 22137-done <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: 22137-done <at> debbugs.gnu.org
Subject: Re: A test of bug #44996
Date: Wed, 12 Mar 2025 19:50:16 -0400

And now I'll re-close and archive this bug.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.