Skip to content
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

bpo-46198: Fix test_asyncio.test_sslproto #31801

Merged
merged 1 commit into from
Mar 10, 2022

Conversation

AlexWaygood
Copy link
Member

@AlexWaygood AlexWaygood commented Mar 10, 2022

GH-30297 removed a duplicate from test import support statement from test_asyncio.test_sslproto. However, in between that PR being filed and it being merged, GH-31275 removed the other from test import support statement. This means that support is now undefined in test_asyncio.test_sslproto, causing the CI to fail on all platforms for all PRs (e.g. https://github.com/python/cpython/runs/5501039134?check_suite_focus=true)

https://bugs.python.org/issue46198

Automerge-Triggered-By: GH:JelleZijlstra

pythonGH-30297 removed a duplicate `from test import support` statement from `test_asyncio.test_sslproto`. However, in between that PR being filed and it being merged, pythonGH-31275 removed the _other_ `from test import support` statement. This means that `support` is now undefined in `test_asyncio.test_sslproto`, causing the CI to fail on all platforms for all PRS.
@bedevere-bot bedevere-bot added the tests Tests in the Lib/test dir label Mar 10, 2022
@AlexWaygood AlexWaygood added type-bug An unexpected behavior, bug, or error skip news labels Mar 10, 2022
Copy link
Member

@JelleZijlstra JelleZijlstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops, thanks for the catch

@JelleZijlstra
Copy link
Member

The backports #31796 and #31797 are unaffected because the other import wasn't removed in the 3.9 and 3.10 branches.

@AlexWaygood
Copy link
Member Author

oops, thanks for the catch

It took a little bit of detective work to figure out how it slipped through the CI!

@JelleZijlstra
Copy link
Member

Thanks for figuring it out!

@merwok
Copy link
Member

merwok commented Mar 11, 2022

I thought we had the check enabled to prevent merging a PR that’s not up to date with the target branch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip news tests Tests in the Lib/test dir type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants