Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34k
bpo-41682: skip test_sendfile_close_peer_in_the_middle_of_receiving in test_asyncio#30801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Conversation
sobolevn commented Jan 22, 2022 • edited by bedevere-bot
Loading Uh oh!
There was an error while loading. Please reload this page.
edited by bedevere-bot
Uh oh!
There was an error while loading. Please reload this page.
… in `test_asyncio`
erlend-aasland commented Jan 22, 2022 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
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. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| @unittest.skipIf(sys.platform.startswith('sunos'), | ||
| "Doesn't work on Solaris") | ||
| @unittest.skipIf(sys.platform=="win32", | ||
| "It is flaky on Windows and needs to be fixed") # TODO: bpo-41682 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: I'd probably include the bug number in the skip message in case that's all the viewer sees.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to not include it in the skip message. Otherwise, https://bugs.python.org/issue41682 will be spammed with pull requests unrelated to the change, if a CI job fails with this message. The bot which mentions PR in bpo searchs for "bpo-xxx" anyway in a PR :-(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ouch!
vstinner left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
miss-islington commented Jan 22, 2022
miss-islington commented Jan 22, 2022
…nGH-30801) (cherry picked from commit 1ded8ed) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
bedevere-bot commented Jan 22, 2022
GH-30811 is a backport of this pull request to the 3.9 branch. |
…nGH-30801) (cherry picked from commit 1ded8ed) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
bedevere-bot commented Jan 22, 2022
GH-30812 is a backport of this pull request to the 3.10 branch. |
gvanrossum commented Jan 23, 2022
Can someone please try to figure out what caused that test to fail, and why it got worse recently? |
vstinner commented Jan 23, 2022
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 |
) (cherry picked from commit 1ded8ed) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
vstinner commented Jan 23, 2022
@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. |
…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