Source: python-uvicorn
Version: 0.13.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/subprocess.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/workers.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/__main__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/logging.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/_types.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/config.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/main.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/importer.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> copying uvicorn/server.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols
> copying uvicorn/protocols/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols
> copying uvicorn/protocols/utils.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols
> creating 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/websockets
> copying uvicorn/protocols/websockets/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/websockets
> copying uvicorn/protocols/websockets/websockets_impl.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/websockets
> copying uvicorn/protocols/websockets/wsproto_impl.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/websockets
> copying uvicorn/protocols/websockets/auto.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/websockets
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/http
> copying uvicorn/protocols/http/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/http
> copying uvicorn/protocols/http/auto.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/http
> copying uvicorn/protocols/http/h11_impl.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/http
> copying uvicorn/protocols/http/httptools_impl.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/protocols/http
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/middleware
> copying uvicorn/middleware/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/middleware
> copying uvicorn/middleware/debug.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/middleware
> copying uvicorn/middleware/wsgi.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/middleware
> copying uvicorn/middleware/asgi2.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/middleware
> copying uvicorn/middleware/message_logger.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/middleware
> copying uvicorn/middleware/proxy_headers.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/middleware
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/loops
> copying uvicorn/loops/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/loops
> copying uvicorn/loops/uvloop.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/loops
> copying uvicorn/loops/asyncio.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/loops
> copying uvicorn/loops/auto.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/loops
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/supervisors
> copying uvicorn/supervisors/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/supervisors
> copying uvicorn/supervisors/watchgodreload.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/supervisors
> copying uvicorn/supervisors/multiprocess.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/supervisors
> copying uvicorn/supervisors/statreload.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/supervisors
> copying uvicorn/supervisors/basereload.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/supervisors
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/lifespan
> copying uvicorn/lifespan/off.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/lifespan
> copying uvicorn/lifespan/__init__.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/lifespan
> copying uvicorn/lifespan/on.py -> 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/uvicorn/lifespan
> running egg_info
> creating uvicorn.egg-info
> writing uvicorn.egg-info/PKG-INFO
> writing dependency_links to uvicorn.egg-info/dependency_links.txt
> writing entry points to uvicorn.egg-info/entry_points.txt
> writing requirements to uvicorn.egg-info/requires.txt
> writing top-level names to uvicorn.egg-info/top_level.txt
> writing manifest file 'uvicorn.egg-info/SOURCES.txt'
> reading manifest file 'uvicorn.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '__pycache__' found anywhere 
> in distribution
> warning: no previously-included files matching '*.py[co]' found anywhere in 
> distribution
> adding license file 'LICENSE.md'
> writing manifest file 'uvicorn.egg-info/SOURCES.txt'
> LC_ALL=C.UTF-8 LANG=C.UTF-8 mkdocs build && mv site html
> INFO    -  Cleaning site directory 
> INFO    -  Building documentation to directory: /<<PKGBUILDDIR>>/site 
> INFO    -  Documentation built in 0.10 seconds 
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:285: cp -r /<<PKGBUILDDIR>>/tests 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build
> I: pybuild base:232: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build; 
> python3.9 -m pytest -k 'not test_run and not test_invalid_upgrade and not 
> test_default_headers and not test_trace_logging'
> ============================= test session starts 
> ==============================
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<<PKGBUILDDIR>>, configfile: setup.cfg
> plugins: mock-3.6.1
> collected 213 items / 16 deselected / 197 selected
> 
> tests/test_auto_detection.py ...                                         [  
> 1%]
> tests/test_cli.py .                                                      [  
> 2%]
> tests/test_client.py ..                                                  [  
> 3%]
> tests/test_config.py ......................                              [ 
> 14%]
> tests/test_lifespan.py ...........                                       [ 
> 19%]
> tests/importer/test_importer.py ......                                   [ 
> 22%]
> tests/middleware/test_debug.py ....                                      [ 
> 24%]
> tests/middleware/test_message_logger.py ..                               [ 
> 25%]
> tests/middleware/test_proxy_headers.py ...                               [ 
> 27%]
> tests/middleware/test_wsgi.py ....                                       [ 
> 29%]
> tests/protocols/test_http.py ........................................... [ 
> 51%]
> .................................FF..........                            [ 
> 74%]
> tests/protocols/test_utils.py ......                                     [ 
> 77%]
> tests/protocols/test_websocket.py ssssssssssssssssssssssssssssssssssss   [ 
> 95%]
> tests/supervisors/test_multiprocess.py .                                 [ 
> 95%]
> tests/supervisors/test_reload.py ........                                
> [100%]
> 
> =================================== FAILURES 
> ===================================
> _________________ test_supported_upgrade_request[H11Protocol] 
> __________________
> 
> protocol_cls = <class 'uvicorn.protocols.http.h11_impl.H11Protocol'>
> 
>     @pytest.mark.parametrize("protocol_cls", HTTP_PROTOCOLS)
>     def test_supported_upgrade_request(protocol_cls):
>         app = Response("Hello, world", media_type="text/plain")
>     
>         protocol = get_connected_protocol(app, protocol_cls, ws="wsproto")
>         protocol.data_received(UPGRADE_REQUEST)
>     
> >       assert b"HTTP/1.1 426 " in protocol.transport.buffer
> E       AssertionError: assert b'HTTP/1.1 426 ' in b'HTTP/1.1 400 
> \r\nSec-WebSocket-Version: 13\r\ncontent-length: 0\r\n\r\n'
> E        +  where b'HTTP/1.1 400 \r\nSec-WebSocket-Version: 
> 13\r\ncontent-length: 0\r\n\r\n' = <test_http.MockTransport object at 
> 0x7f5dfc10cf10>.buffer
> E        +    where <test_http.MockTransport object at 0x7f5dfc10cf10> = 
> <uvicorn.protocols.http.h11_impl.H11Protocol object at 
> 0x7f5dfc104fd0>.transport
> 
> tests/protocols/test_http.py:685: AssertionError
> ______________ test_supported_upgrade_request[HttpToolsProtocol] 
> _______________
> 
> protocol_cls = <class 
> 'uvicorn.protocols.http.httptools_impl.HttpToolsProtocol'>
> 
>     @pytest.mark.parametrize("protocol_cls", HTTP_PROTOCOLS)
>     def test_supported_upgrade_request(protocol_cls):
>         app = Response("Hello, world", media_type="text/plain")
>     
>         protocol = get_connected_protocol(app, protocol_cls, ws="wsproto")
>         protocol.data_received(UPGRADE_REQUEST)
>     
> >       assert b"HTTP/1.1 426 " in protocol.transport.buffer
> E       AssertionError: assert b'HTTP/1.1 426 ' in b'HTTP/1.1 400 
> \r\nSec-WebSocket-Version: 13\r\ncontent-length: 0\r\n\r\n'
> E        +  where b'HTTP/1.1 400 \r\nSec-WebSocket-Version: 
> 13\r\ncontent-length: 0\r\n\r\n' = <test_http.MockTransport object at 
> 0x7f5dfb815af0>.buffer
> E        +    where <test_http.MockTransport object at 0x7f5dfb815af0> = 
> <uvicorn.protocols.http.httptools_impl.HttpToolsProtocol object at 
> 0x7f5dfb815670>.transport
> 
> tests/protocols/test_http.py:685: AssertionError
> =============================== warnings summary 
> ===============================
> tests/test_default_headers.py:14
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_default_headers.py:14:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_default_headers.py:23
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_default_headers.py:23:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_default_headers.py:39
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_default_headers.py:39:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_default_headers.py:56
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_default_headers.py:56:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_main.py:14
>   /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_main.py:14: 
> PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_main.py:31
>   /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_main.py:31: 
> PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_main.py:40
>   /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_main.py:40: 
> PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_ssl.py:14
>   /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_ssl.py:14: 
> PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_ssl.py:29
>   /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_ssl.py:29: 
> PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/test_ssl.py:43
>   /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/test_ssl.py:43: 
> PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/middleware/test_trace_logging.py:53
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/middleware/test_trace_logging.py:53:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/middleware/test_trace_logging.py:71
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/middleware/test_trace_logging.py:71:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:43
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:43:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:73
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:73:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:90
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:90:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:110
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:110:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:130
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:130:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:151
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:151:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:169
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:169:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:187
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:187:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:213
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:213:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:235
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:235:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:257
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:257:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:285
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:285:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:301
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:301:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:317
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:317:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:335
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:335:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:358
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:358:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:384
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:384:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> tests/protocols/test_websocket.py:407
>   
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py:407:
>  PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo?  You 
> can register custom marks to avoid this warning - for details, see 
> https://docs.pytest.org/en/stable/mark.html
>     @pytest.mark.asyncio
> 
> .pybuild/cpython3_3.9/build/tests/protocols/test_websocket.py: 36 warnings
>   /usr/lib/python3/dist-packages/_pytest/python.py:172: 
> PytestUnhandledCoroutineWarning: async def functions are not natively 
> supported and have been skipped.
>   You need to install a suitable plugin for your async framework, for example:
>     - anyio
>     - pytest-asyncio
>     - pytest-tornasync
>     - pytest-trio
>     - pytest-twisted
>     warnings.warn(PytestUnhandledCoroutineWarning(msg.format(nodeid)))
> 
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> =========================== short test summary info 
> ============================
> SKIPPED [36] 
> ../../../../../../usr/lib/python3/dist-packages/_pytest/python.py:173: async 
> def function and no async plugin installed (see warnings)
> ==== 2 failed, 159 passed, 36 skipped, 16 deselected, 66 warnings in 2.78s 
> =====
> E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1: cd 
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build; python3.9 -m pytest -k 'not 
> test_run and not test_invalid_upgrade and not test_default_headers and not 
> test_trace_logging'
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-uvicorn_0.13.3-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to