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
if you have a class containing some shared tests (e.g. for contract testing between several implementations of an interface), and use both hypothesis and pytest-asyncio on the shared tests, pytest will raise an error when running the test for the second time.
i have no idea what the inner workings are here but it looks like the corountine is associated to an event loop, then cached and it tries to run it again after that event loop is closed?
removing either hypothesis or pytest-asyncio makes it work as expected, its only when both are in play that the error appears.
This is probably a pytest-asyncio error - I know that they have Hypothesis integration, but we don't have any special logic for asyncio. Wish I could be more helpful 😕
if you have a class containing some shared tests (e.g. for contract testing between several implementations of an interface), and use both
hypothesis
andpytest-asyncio
on the shared tests, pytest will raise an error when running the test for the second time.i have no idea what the inner workings are here but it looks like the corountine is associated to an event loop, then cached and it tries to run it again after that event loop is closed?
removing either hypothesis or pytest-asyncio makes it work as expected, its only when both are in play that the error appears.
minimal test case
output
environment
The text was updated successfully, but these errors were encountered: