| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Feature or enhancement
Get rid of ad-hoc implementation of async tests by using all relatively new features of standard IsolatedAsyncIoTestCase. For this we need to:
Pitch
Progress tracking
| Back | FazBrowse Home | New Git URL |
Activity
gh-93357: Start porting asyncio server test cases to IsolatedAsyncioT…
gh-93357: Port test cases to IsolatedAsyncioTestCase, part 2 (#97896)
Merge branch 'main' into dictwatch
Revert "pythongh-93357: Port test cases to IsolatedAsyncioTestCase, p…
Revert "pythongh-93357: Start porting asyncio server test cases to Is…
gh-97983: Revert "Lay the foundation for further work in asyncio.test…
pythongh-93357: Start porting asyncio server test cases to IsolatedAs…
pythongh-93357: Port test cases to IsolatedAsyncioTestCase, part 2 (p…
pythongh-97983: Revert "Lay the foundation for further work in asynci…
kumaraditya303 commented on Oct 27, 2022
If we want to continue with this, then IMO this needs to be done early in the dev cycle so we have time to fixup the CI if it breaks. We certainly don't want to deal with unstable CI at the beta stage.
arhadthedev commented on Oct 27, 2022
@kumaraditya303 You're right; I'll return to this issue this weekend and start with stabilization of reverted gh-98015.
arhadthedev commented on Oct 30, 2022
Put on hold until gh-98219 is resolved (it probably will fix Altered environment on Windows and Env changed in buildbot in gh-97983).
kumaraditya303 commented on Apr 19, 2023
I'm going to just close this now, it is not the best use of our time to port these tests as it doesn't increase test coverage and chance of breaking CI is very high especially as asyncio is very flaky. When I'll remove child watcher I may port some tests to ease writing new tests but not other things.