8000 [3.6] bpo-31310: multiprocessing's semaphore tracker should be launched again if crashed (GH-3247) by pitrou · Pull Request #4254 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

[3.6] bpo-31310: multiprocessing's semaphore tracker should be launched again if crashed (GH-3247) #4254

New issue 8000

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Nov 3, 2017
Merged

[3.6] bpo-31310: multiprocessing's semaphore tracker should be launched again if crashed (GH-3247) #4254

merged 1 commit into from
Nov 3, 2017

Conversation

pitrou
Copy link
Member
@pitrou pitrou commented Nov 3, 2017 •
edited by bedevere-bot
Loading

@pitrou
[3.6] bpo-31310: multiprocessing's semaphore tracker should be launch…
5623e3a 
…ed again if crashed (pythonGH-3247)

* bpo-31310: multiprocessing's semaphore tracker should be launched again if crashed

* Avoid mucking with process state in test.
Add a warning if the semaphore process died, as semaphores may then be leaked.

* Add NEWS entry
(cherry picked from commit cbe1756)
@pitrou pitrou merged commit b5f09ac into python:3.6 Nov 3, 2017
@pitrou pitrou deleted the backport-cbe1756-3.6 branch November 3, 2017 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@pitrou @the-knights-who-say-ni @bedevere-bot
0