pytest-dev / pytest-dev/pytest-xdist
unclosed sockets - ResourceWarning
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 287
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 2
Description
/Users/bgabor8/git/binder/repo2docker/.tox/py37/lib/python3.7/site-packages/_pytest/runner.py:99
/Users/bgabor8/git/binder/repo2docker/.tox/py37/lib/python3.7/site-packages/_pytest/runner.py:99
/Users/bgabor8/git/binder/repo2docker/.tox/py37/lib/python3.7/site-packages/_pytest/runner.py:99
/Users/bgabor8/git/binder/repo2docker/.tox/py37/lib/python3.7/site-packages/_pytest/runner.py:99: ResourceWarning: unclosed <socket.socket fd=14, family=AddressFamily.AF_UNIX, type=SocketKind.SOCK_STREAM, proto=0, raddr=docker.sock>
item.funcargs = None
Contributor guide
No contributing guide indexed for this repository
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
The report contains only a pytest runner traceback and a ResourceWarning for an unclosed Unix socket connected to docker.sock. Start by reproducing the warning in pytest-xdist's distributed testing context and trace which socket lifecycle leaves it open; done means the warning no longer appears and the relevant tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100