Re-enable gdb stubtest
Open
Nobody has claimed this yet.
project: infrastructure
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.1k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 82
Description
#15235 did disable stubtest for gdb, due to the following error:
Traceback (most recent call last):
File "/tmp/stubtest-lhvl4qwb/gdb_stubtest.py", line 22, in <module>
from mypy.stubtest import main
File "/tmp/stubtest-lhvl4qwb/lib/python3.13/site-packages/mypy/stubtest.py", line 36, in <module>
import mypy.build
File "/tmp/stubtest-lhvl4qwb/lib/python3.13/site-packages/mypy/build.py", line 31, in <module>
from librt.internal import cache_version
ModuleNotFoundError: No module named 'librt.internal'
This might be related to unsetting LD_LIBRARY_PATH in stubtest_third_party.py. In any case, we should find the error and re-enable stubtest for gdb.
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 stubtest_third_party.py and the gdb stubtest setup, then reproduce the shown ModuleNotFoundError for librt.internal while checking the effect of unsetting LD_LIBRARY_PATH. Trace the environment or dependency issue until gdb stubtest runs again, and confirm that stubtest is re-enabled for gdb.
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
- Mostly clear
- Newbie friendliness
- 35/100