test_multiprocessing_fork probabilistic failure
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
tests
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 47249 |
|---|---|
| Files |
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 2022-04-07.13:41:52.675>
labels = ['type-bug', 'tests', '3.9', '3.10', '3.11']
title = 'test_multiprocessing_fork probabilistic failure'
updated_at = <Date 2022-04-07.13:50:37.734>
user = 'https://bugs.python.org/sxt1001'
bugs.python.org fields:
activity = <Date 2022-04-07.13:50:37.734>
actor = 'sxt1001'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2022-04-07.13:41:52.675>
creator = 'sxt1001'
dependencies = []
files = ['50726']
hgrepos = []
issue_num = 47249
keywords = []
message_count = 2.0
messages = ['416926', '416927']
nosy_count = 1.0
nosy_names = ['sxt1001']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue47249'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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
Start by locating and running the test_multiprocessing_fork test, then read BPO issue 47249 and inspect the attached test hang screenshot. The issue does not identify a failing assertion or expected change; completion would require determining the cause of the probabilistic failure and making the test reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100