Bug 1817681

Thanks for the upstream pull request reference Petr.  That is part of upstream 1.3.0.  I updated the spec file locally to that version, but it still fails with the python39 copr.


=================================== FAILURES ===================================
______________________ test_run_natively[asyncio-asyncio] ______________________
tests/test_taskgroups.py:60: in test_run_natively
    module.run(testfunc())
/usr/lib64/python3.9/asyncio/runners.py:48: in run
    loop.run_until_complete(loop.shutdown_default_executor())
uvloop/loop.pyx:1451: in uvloop.loop.Loop.run_until_complete
    ???
/usr/lib64/python3.9/asyncio/events.py:254: in shutdown_default_executor
    raise NotImplementedError
E   NotImplementedError
__________________ test_run_natively[asyncio+uvloop-asyncio] ___________________
tests/test_taskgroups.py:60: in test_run_natively
    module.run(testfunc())
/usr/lib64/python3.9/asyncio/runners.py:48: in run
    loop.run_until_complete(loop.shutdown_default_executor())
uvloop/loop.pyx:1451: in uvloop.loop.Loop.run_until_complete
    ???
/usr/lib64/python3.9/asyncio/events.py:254: in shutdown_default_executor
    raise NotImplementedError
E   NotImplementedError
_______________________ test_run_natively[curio-asyncio] _______________________
tests/test_taskgroups.py:60: in test_run_natively
    module.run(testfunc())
/usr/lib64/python3.9/asyncio/runners.py:48: in run
    loop.run_until_complete(loop.shutdown_default_executor())
uvloop/loop.pyx:1451: in uvloop.loop.Loop.run_until_complete
    ???
/usr/lib64/python3.9/asyncio/events.py:254: in shutdown_default_executor
    raise NotImplementedError
E   NotImplementedError
_______________________ test_run_natively[trio-asyncio] ________________________
tests/test_taskgroups.py:60: in test_run_natively
    module.run(testfunc())
/usr/lib64/python3.9/asyncio/runners.py:48: in run
    loop.run_until_complete(loop.shutdown_default_executor())
uvloop/loop.pyx:1451: in uvloop.loop.Loop.run_until_complete
    ???
/usr/lib64/python3.9/asyncio/events.py:254: in shutdown_default_executor
    raise NotImplementedError
E   NotImplementedError
______________________ test_spawn_while_running[asyncio] _______________________
../../BUILDROOT/python-anyio-1.3.0-1.fc33.x86_64/usr/lib/python3.9/site-packages/anyio/pytest_plugin.py:115: in pytest_pyfunc_call
    run(partial(pyfuncitem.obj, **testargs), backend=backend,
../../BUILDROOT/python-anyio-1.3.0-1.fc33.x86_64/usr/lib/python3.9/site-packages/anyio/__init__.py:68: in run
    return asynclib.run(func, *args, **backend_options)  # type: ignore
../../BUILDROOT/python-anyio-1.3.0-1.fc33.x86_64/usr/lib/python3.9/site-packages/anyio/_backends/_asyncio.py:93: in run
    loop = asyncio.get_event_loop()
/usr/lib64/python3.9/asyncio/events.py:643: in get_event_loop
    raise RuntimeError('There is no current event loop in thread %r.'
E   RuntimeError: There is no current event loop in thread 'MainThread'.
=============================== warnings summary ===============================
/usr/lib/python3.9/site-packages/outcome/_sync.py:43
  /usr/lib/python3.9/site-packages/outcome/_sync.py:43: DeprecationWarning: The usage of `cmp` is deprecated and will be removed on or after 2021-06-01.  Please use `eq` and `order` instead.
    _unwrapped = attr.ib(default=False, cmp=False, init=False)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
============== 5 failed, 478 passed, 1 warnings in 10.07 seconds ===============
error: Bad exit status from /var/tmp/rpm-tmp.YIf74v (%check)
    Bad exit status from /var/tmp/rpm-tmp.YIf74v (%check)

Thank you! This might be a bug in asyncio.
I'm a bit out of my depth here, so I asked on the bug that added shutdown_default_executor: https://bugs.python.org/issue34037#msg366812

This comment is mass posted to all bugs blocking the Python 3.9 tracker, sorry if it is not 100 % relevant. When in doubt, please ask.


The Python 3.9 rebuild is in progress in a Koji side tag.

If you fix this bug, please don't rebuild the package in regular rawhide, but do it in the side tag with:

    $ fedpkg build --target=f33-python

The rebuild is progressing slowly and it is possible this package won't have all the required build dependencies yet. If that's the case, please just leave the fix committed and pushed and we will eventually rebuild it for you.

You are not asked to go and try rebuild all the missing dependencies yourself. If you know there is a bootstrap loop in the dependencies, let me know and we can untangle it together.

If you want to test your fix or reproduce the failure, you can still use the Copr repo mentioned in the initial comment of this bug: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/

Reported upstream.

https://github.com/agronholm/anyio/issues/110

Python 3.9 update: The f33-python side tag is currently being merged.

New builds in f33-python are no longer possible, but python3 is not yet updated to Python 3.9 in rawhide. You can check when Python is Python 3.9 with:

    $ koji wait-repo f33-build --build python3.9-3.9.0~b1-3.fc3

And build the packages normally after that.

Upstream released version 1.3.1 that resolved this.

https://bodhi.fedoraproject.org/updates/FEDORA-2020-29203271e7