-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
running stdlib asyncio unittests again #6927
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
running stdlib asyncio unittests again #6927
Conversation
i tried a few approaches to sort out the async result, i'll take a good night of sleep and try again its likely going to require a semi-permanent hack in |
ec2cb0f
to
b2aadb8
Compare
Another thought is to update the hook to also somehow forward the result of the function call forward (and hence the async result). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix.
Missing the CHANGELOG to 😁
0f17bef
to
e216752
Compare
shoehorn unittest async results into python test result interpretation changelog
e216752
to
451aef6
Compare
merged as admin due to the unrelated py37 windows failure |
Sorry, I just realized we have forgotten to backport this to |
…n-async-stdlib-unittests running stdlib asyncio unittests again
…nc-unittest backport #6927: run async testcase methods
fixes #6924
opting out of the warning+skip revealed that the generators currently don't execute, while on 5.3 they do by accidennt