GeezerVison

All commit authors signed the Contributor License Agreement.

Hi,

is there anything I could do to help unblock this PR? I don't know what is the expected review time for such bug-fixes. I don't know if they are reviewed in bulk every N-weeks or if we don't hear back after a few days it's a bad sign.

@kumaraditya303 I think this is related to #159073.

@jblespiau you're going to need to update this to account for changes made there.

Updated and rebased on HEAD.

I think it's done, and I rebased on head again. Github is showing me it's "processing updates".

if this version still need changes, maybe it would be easier if a Python maintainer takes over as they are more familar with the tooling, tests, code, etc. As there is a reproducer, it should already help quite a lot.

the test passes after the CL, and fails on the assert Assertion 'task->task_state == STATE_PENDING' failed (Aborted). from head, and with this removed, it fails with Fatal Python error: Segmentation fault.

I don't know why, but what I see inthe PR isn't what I have in the branch in my fork:

main...jblespiau:cpython:fix-asyncio-task-unregister-race

Thanks @jblespiau for the PR, and @kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15.
🐍🍒⛏🤖

Sorry, @jblespiau and @kumaraditya303, I could not cleanly backport this to 3.14 due to a conflict.

Please backport manually with cherry_picker, see the devguide for more information.

cherry_picker aaaf61ca62f0924d7b5134c2d237313d8be2215c 3.14

GH-161379 is a backport of this pull request to the 3.15 branch.

GH-161380 is a backport of this pull request to the 3.14 branch.

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 FreeBSD Refleaks 3.15 (tier-3) has failed when building commit 3619efa.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/2056/builds/487) and take a look at the build logs.
4. Check if the failure is related to this commit (3619efa) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/2056/builds/487

Failed tests:

• test.test_asyncio.test_ssl

Failed subtests:

• test_remote_shutdown_receives_trailing_data - test.test_asyncio.test_ssl.TestSSL.test_remote_shutdown_receives_trailing_data

Summary of the results of the build (if available):

==

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.15.opsec-fbsd14.refleak/build/Lib/test/test_asyncio/test_ssl.py", line 1430, in test_remote_shutdown_receives_trailing_data
    self.loop.run_until_complete(client(srv.addr))
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.15.opsec-fbsd14.refleak/build/Lib/asyncio/base_events.py", line 730, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "/home/buildbot/buildarea/3.15.opsec-fbsd14.refleak/build/Lib/test/test_asyncio/test_ssl.py", line 1414, in client
    await future
  File "/home/buildbot/buildarea/3.15.opsec-fbsd14.refleak/build/Lib/test/test_asyncio/test_ssl.py", line 1422, in wrapper
    meth(sock)
    ~~~~^^^^^^
  File "/home/buildbot/buildarea/3.15.opsec-fbsd14.refleak/build/Lib/test/test_asyncio/test_ssl.py", line 1368, in server
    self.assertEqual(data_len, CHUNK * SIZE)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 0 != 4194304