You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
IsolatedAsyncioTestCase calls _setupAsyncioRunner even for skipped tests #96030
TestCase.run() is always executed, even for skipped tests. In fact the method checks for skipped and expected failure markers. The implementation of IsolatedAsyncioTestCase.run runs additional code around TestCase.run that does not obey the skipped marker. This was first discovered when GH-95736 broke tests on wasm32-emscripten. _setupAsyncioRunner should not be called if a test method or class is marked as skipped.
changed the title [-]IsolatedAsyncioTestCase sets up asyncio runner for skipped tests[/-][+]IsolatedAsyncioTestCase calls _setupAsyncioRunner even for skipped tests[/+]on Aug 16, 2022
Activity
pythongh-96030: IsolatedAsyncioTestCase: don't create asyncio runner …
pythongh-96030: IsolatedAsyncioTestCase: don't create asyncio runner …
gvanrossum commentedon Aug 16, 2022
Maybe #96033 was meant to fix this too?
[-]IsolatedAsyncioTestCase sets up asyncio runner for skipped tests[/-][+]IsolatedAsyncioTestCase calls _setupAsyncioRunner even for skipped tests[/+]kumaraditya303 commentedon Oct 30, 2022
AFAIK this is already fixed by #96033.