bpo-26552: Fixed case where failing `asyncio.ensure_future` did not close the coroutine by kumaraditya303 · Pull Request #30288 · python/cpython · GitHub
GitHub CopilotWrite better code with AI | MCP RegistryIntegrate external tools | ActionsAutomate any workflow | CodespacesInstant dev environments | IssuesPlan and track work | Code ReviewManage code changes | Code QualityEnforce quality at merge | Why GitHub | Marketplace | View all features | Enterprises | Small and medium teams | Startups | View all use cases | View all industries | View all solutions | AI | Software Development | DevOps | Security | View all topics | Customer stories | Events & webinars | Ebooks & reports | Business insights | Trust center | Partners | View all resources
Tin mới
GitHub CopilotWrite better code with AI
GitHub Copilot appDirect agents from issue to merge
CodespacesInstant dev environments
Code ReviewManage code changes
Code QualityEnforce quality at merge
GitHub Advanced SecurityFind and fix vulnerabilities
Code securitySecure your code as you build
Secret protectionStop leaks before they start
GitHub SponsorsFund open source developers
Copilot for BusinessEnterprise-grade AI features
Premium SupportEnterprise-grade 24/7 support
bpo-26552: fix failing ensure_future still creates a Task
test_asyncio random failures on a Windows runner
*with hope* Does it fix test_asyncio random failures on a Windows runner so it can be enabled back?
Learn more about hiding disruptive comments
The reason will be displayed to describe this comment to others. Learn more.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot PPC64LE CentOS9 3.x has failed when building commit 24cc641.
bpo-26552: Fixed case where failing asyncio.ensure_future did not c…