Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #13894 > unrolled thread

python-anyio failing testsuite on buildd, not locally

Started byJulien Puydt <julien.puydt@gmail.com>
First post2022-01-19 17:00 +0100
Last post2022-01-21 14:10 +0100
Articles 3 — 3 participants

Back to article view | Back to linux.debian.maint.python

Contents

  python-anyio failing testsuite on buildd, not locally Julien Puydt <julien.puydt@gmail.com> - 2022-01-19 17:00 +0100
    Re: python-anyio failing testsuite on buildd, not locally Emmanuel Arias <eamanu@yaerobi.com> - 2022-01-21 13:50 +0100
      Re: python-anyio failing testsuite on buildd, not locally Julien Cristau <jcristau@debian.org> - 2022-01-21 14:10 +0100

#13894 — python-anyio failing testsuite on buildd, not locally

FromJulien Puydt <julien.puydt@gmail.com>
Date2022-01-19 17:00 +0100
Subjectpython-anyio failing testsuite on buildd, not locally
Message-ID<DHlxn-5QD-3@gated-at.bofh.it>
Hi,

I check my packages in a schroot on my computer before uploading ; that
way I detect problems like missing deps or network access, and I'm
pretty confident things will go well on the buildd network.

But today's upload of python-anyio is broken... and I'm clueless as to
why. From the repeated error, it looks like 'localhost' isn't known,
which doesn't make sense.

Here is a link to the full log:
https://buildd.debian.org/status/fetch.php?pkg=python-anyio&arch=all&ver=3.5.0-1&stamp=1642600026&raw=0

and a sample error:

__________________ TestTCPListener.test_accept[asyncio-ipv4]
___________________
tests/test_sockets.py:464: in test_accept
    async with await create_tcp_listener(local_host='localhost',
family=family) as multi:
anyio/_core/_sockets.py:236: in create_tcp_listener
    gai_res = await getaddrinfo(local_host, local_port, family=family,
# type: ignore[arg-type]
anyio/_core/_sockets.py:419: in getaddrinfo
    gai_res = await get_asynclib().getaddrinfo(encoded_host, port,
family=family, type=type,
anyio/_backends/_asyncio.py:1570: in getaddrinfo
    result = await get_running_loop().getaddrinfo(
/usr/lib/python3.9/asyncio/base_events.py:856: in getaddrinfo
    return await self.run_in_executor(
/usr/lib/python3.9/concurrent/futures/thread.py:58: in run
    result = self.fn(*self.args, **self.kwargs)
/usr/lib/python3.9/asyncio/base_events.py:839: in _getaddrinfo_debug
    addrinfo = socket.getaddrinfo(host, port, family, type, proto,
flags)
/usr/lib/python3.9/socket.py:954: in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto,
flags):
E   socket.gaierror: [Errno -2] Name or service not known

If someone has a lead on the issue...

Thanks,

J.Puydt

[toc] | [next] | [standalone]

#13896

FromEmmanuel Arias <eamanu@yaerobi.com>
Date2022-01-21 13:50 +0100
Message-ID<DI1wB-6r4-7@gated-at.bofh.it>
In reply to#13894

[Multipart message — attachments visible in raw view] — view raw

Hi,

Most of the tests that fail use *-ipv4 parameter. With ipv6 seems to be ok.
I don't know if that can give us some clues.

Cheers,

On Wed, Jan 19, 2022 at 12:52 PM Julien Puydt <julien.puydt@gmail.com>
wrote:

> Hi,
>
> I check my packages in a schroot on my computer before uploading ; that
> way I detect problems like missing deps or network access, and I'm
> pretty confident things will go well on the buildd network.
>
> But today's upload of python-anyio is broken... and I'm clueless as to
> why. From the repeated error, it looks like 'localhost' isn't known,
> which doesn't make sense.
>
> Here is a link to the full log:
>
> https://buildd.debian.org/status/fetch.php?pkg=python-anyio&arch=all&ver=3.5.0-1&stamp=1642600026&raw=0
>
> and a sample error:
>
> __________________ TestTCPListener.test_accept[asyncio-ipv4]
> ___________________
> tests/test_sockets.py:464: in test_accept
>     async with await create_tcp_listener(local_host='localhost',
> family=family) as multi:
> anyio/_core/_sockets.py:236: in create_tcp_listener
>     gai_res = await getaddrinfo(local_host, local_port, family=family,
> # type: ignore[arg-type]
> anyio/_core/_sockets.py:419: in getaddrinfo
>     gai_res = await get_asynclib().getaddrinfo(encoded_host, port,
> family=family, type=type,
> anyio/_backends/_asyncio.py:1570: in getaddrinfo
>     result = await get_running_loop().getaddrinfo(
> /usr/lib/python3.9/asyncio/base_events.py:856: in getaddrinfo
>     return await self.run_in_executor(
> /usr/lib/python3.9/concurrent/futures/thread.py:58: in run
>     result = self.fn(*self.args, **self.kwargs)
> /usr/lib/python3.9/asyncio/base_events.py:839: in _getaddrinfo_debug
>     addrinfo = socket.getaddrinfo(host, port, family, type, proto,
> flags)
> /usr/lib/python3.9/socket.py:954: in getaddrinfo
>     for res in _socket.getaddrinfo(host, port, family, type, proto,
> flags):
> E   socket.gaierror: [Errno -2] Name or service not known
>
> If someone has a lead on the issue...
>
> Thanks,
>
> J.Puydt
>
>

[toc] | [prev] | [next] | [standalone]

#13897

FromJulien Cristau <jcristau@debian.org>
Date2022-01-21 14:10 +0100
Message-ID<DI1PX-6MX-1@gated-at.bofh.it>
In reply to#13896
Hi,

x86-conova-01 has no ipv4 address other than loopback.  That causes
getaddrinfo with the AI_ADDRCONFIG flag to not return ipv4 addresses.

See also https://lists.debian.org/debian-devel/2020/07/msg00070.html

Cheers,
Julien

On Fri, Jan 21, 2022 at 09:43:40AM -0300, Emmanuel Arias wrote:
> Hi, 
> 
> Most of the tests that fail use *-ipv4 parameter. With ipv6 seems to be ok.
> I don't know if that can give us some clues.
> 
> Cheers,
> 
> On Wed, Jan 19, 2022 at 12:52 PM Julien Puydt <julien.puydt@gmail.com> wrote:
> 
>     Hi,
> 
>     I check my packages in a schroot on my computer before uploading ; that
>     way I detect problems like missing deps or network access, and I'm
>     pretty confident things will go well on the buildd network.
> 
>     But today's upload of python-anyio is broken... and I'm clueless as to
>     why. From the repeated error, it looks like 'localhost' isn't known,
>     which doesn't make sense.
> 
>     Here is a link to the full log:
>     https://buildd.debian.org/status/fetch.php?pkg=python-anyio&arch=all&ver=
>     3.5.0-1&stamp=1642600026&raw=0
> 
>     and a sample error:
> 
>     __________________ TestTCPListener.test_accept[asyncio-ipv4]
>     ___________________
>     tests/test_sockets.py:464: in test_accept
>         async with await create_tcp_listener(local_host='localhost',
>     family=family) as multi:
>     anyio/_core/_sockets.py:236: in create_tcp_listener
>         gai_res = await getaddrinfo(local_host, local_port, family=family,
>     # type: ignore[arg-type]
>     anyio/_core/_sockets.py:419: in getaddrinfo
>         gai_res = await get_asynclib().getaddrinfo(encoded_host, port,
>     family=family, type=type,
>     anyio/_backends/_asyncio.py:1570: in getaddrinfo
>         result = await get_running_loop().getaddrinfo(
>     /usr/lib/python3.9/asyncio/base_events.py:856: in getaddrinfo
>         return await self.run_in_executor(
>     /usr/lib/python3.9/concurrent/futures/thread.py:58: in run
>         result = self.fn(*self.args, **self.kwargs)
>     /usr/lib/python3.9/asyncio/base_events.py:839: in _getaddrinfo_debug
>         addrinfo = socket.getaddrinfo(host, port, family, type, proto,
>     flags)
>     /usr/lib/python3.9/socket.py:954: in getaddrinfo
>         for res in _socket.getaddrinfo(host, port, family, type, proto,
>     flags):
>     E   socket.gaierror: [Errno -2] Name or service not known
> 
>     If someone has a lead on the issue...
> 
>     Thanks,
> 
>     J.Puydt
> 
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web