Tracking test_gil_scoped.py `DEADLOCK`s
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
Using this Issue to track test_gil_scoped.py failures like this one:
E RuntimeError: DEADLOCK, most likely, exactly what this test is meant to detect.
Background: PRs #4105, #4306
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 with test_gil_scoped.py and compare the DEADLOCK failure with the context in PRs #4105 and #4306. Trace the reported RuntimeError from the test; done means the tracked failures have an identified resolution and no longer remain unexplained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, 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