• python-anyio failing testsuite on buildd, not locally

    From Julien Puydt@21:1/5 to All on Wed Jan 19 17:00:01 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Julien Cristau@21:1/5 to Emmanuel Arias on Fri Jan 21 14:10:01 2022
    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



    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Emmanuel Arias@21:1/5 to All on Fri Jan 21 13:50:02 2022
    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



    <div dir="ltr"><div>Hi, </div><div><br></div>Most of the tests that fail use *-<span style="color:rgb(0,0,0)">ipv4 parameter. With ipv6 seems to be ok.</span><div><span style="color:rgb(0,0,0)">I don&#39;t know if that can give us some clues.</span></
    <div><span style="color:rgb(0,0,0)"><br></span></div><div><span style="color:rgb(0,0,0)">Cheers,</span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 19, 2022 at 12:52 PM Julien Puydt &lt;<a href="mailto:julien.
    puydt@gmail.com">julien.puydt@gmail.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>

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

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

    Here is a link to the full log:<br>
    <a href="https://buildd.debian.org/status/fetch.php?pkg=python-anyio&amp;arch=all&amp;ver=3.5.0-1&amp;stamp=1642600026&amp;raw=0" rel="noreferrer" target="_blank">https://buildd.debian.org/status/fetch.php?pkg=python-anyio&amp;arch=all&amp;ver=3.5.0-1&
    amp;stamp=1642600026&amp;raw=0</a><br>

    and a sample error:<br>

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

    If someone has a lead on the issue...<br>

    Thanks,<br>

    J.Puydt<br>

    </blockquote></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)