Skip to content

[3.6] bpo-33469: RuntimeError after closing loop that used run_in_executor (GH-7171) #7179

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

Merged
merged 1 commit into from
May 29, 2018

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented May 28, 2018

(cherry picked from commit fdccfe0)

Co-authored-by: Yury Selivanov yury@magic.io

https://bugs.python.org/issue33469

…ythonGH-7171)

(cherry picked from commit fdccfe0)

Co-authored-by: Yury Selivanov <yury@magic.io>
@miss-islington
Copy link
Contributor Author

@1st1: Backport status check is done, and it's a failure ❌ .

@vstinner
Copy link
Member

@1st1: I am sorry, I cancelled the AppVeyor job because I'm waiting since 2 hours for AppVeyor to run on my PR #7175 which blocks 3.7rc1 release. On this PR, the VS 2017 job of AppVeyor was "queued" since 31 min, whereas the "VS 2015" job completed. Please retrigger manually the job.

@vstinner
Copy link
Member

Please retrigger manually the job.

Hum, I just did that: re-trigger the AppVeyor job.

@miss-islington
Copy link
Contributor Author

@1st1: Backport status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit a6d6bd7 into python:3.6 May 29, 2018
@miss-islington
Copy link
Contributor Author

Thanks!

@miss-islington miss-islington deleted the backport-fdccfe0-3.6 branch May 29, 2018 01:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants