bpo-41682: skip test_sendfile_close_peer_in_the_middle_of_receiving in test_asyncio#30801
bpo-41682: skip test_sendfile_close_peer_in_the_middle_of_receiving in test_asyncio#30801vstinner merged 3 commits into
test_sendfile_close_peer_in_the_middle_of_receiving in test_asyncio#30801Conversation
… in `test_asyncio`
|
If I remember correctly, all failures are on Windows. Perhaps we can skip on Windows only? I generally don't feel comfortable with just skipping a flakey test; it tends to lead to the issue being forgotten and possibly hiding real bugs. OTOH, the noise level on the CI is unbearable at the moment. |
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
LGTM. I would prefer to fix it, but well, since Septembre 2020, no one was available to investigate this bug, whereas this bug annoys anyone paying attention to Python CIs for 1 year and a half.
But please don't close https://bugs.python.org/issue41682 until the real issue is fixed.
Sorry, something went wrong.
…nGH-30801) (cherry picked from commit 1ded8ed) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
…nGH-30801) (cherry picked from commit 1ded8ed) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
|
Can someone please try to figure out what caused that test to fail, and why it got worse recently? |
Sorry, something went wrong.
I also noticed that the step started to fail more recently recently. Maybe a CI updated Windows. I saw an announcement that Azure Pipelines or GitHub Actions (oops, I don't recall anymore) is being upgrade incrementally to Windows Server 2022, for example. About the bug itself, it has been reported in September 2020 and so far, no one was available to investigate the issue: https://bugs.python.org/issue41682 |
Sorry, something went wrong.
) (cherry picked from commit 1ded8ed) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
@zooba modified the config yesterday to request explicitly Windows 2022 for the Windows jobs of the Azure Pipelines: commit 70c1646. My PR #30817 confirms that Windows Server 2022 is now used on Azure Pipelines for the Windows jobs. So maybe the test fails more frequently or always fails on Windows Server 2022. |
Sorry, something went wrong.
…nGH-30801) (cherry picked from commit 1ded8ed) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
It is failing way too often:

Most of the commits above failed due to this single test.
I don't know how to fix it, but at least we can decrease the noise.
https://bugs.python.org/issue41682