unittest blocks when testing function using multiprocessing.Pool with state spawn
Open
Nobody has claimed this yet.
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33054 |
|---|---|
| Nosy | @pitrou |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2018-03-12.13:12:55.379>
labels = ['type-bug']
title = 'unittest blocks when testing function using multiprocessing.Pool with state spawn'
updated_at = <Date 2018-03-13.22:06:33.152>
user = 'https://bugs.python.org/KennethChik'
bugs.python.org fields:
activity = <Date 2018-03-13.22:06:33.152>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2018-03-12.13:12:55.379>
creator = 'Kenneth Chik'
dependencies = []
files = []
hgrepos = []
issue_num = 33054
keywords = []
message_count = 2.0
messages = ['313648', '313787']
nosy_count = 2.0
nosy_names = ['pitrou', 'Kenneth Chik']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33054'
versions = ['Python 3.6']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named in the issue. Start by reproducing the unittest hang with multiprocessing.Pool using the spawn state, then trace the interaction between unittest and Pool; done means the reported test no longer blocks under that configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100