Debugging unit tests is not working, but running tests is possible

[FrancaBa]

Type: Bug

Behaviour

Expected vs. Actual

I used to be able to debug tests through the python testing extension. Since end of November, I am not able to debug in vsc through this extension anymore. However, running tests in the extension is still possible. I get following error message:

Error[vscode-unittest]: RUN_TEST_IDS_PORT env var is not set.
Error: Could not connect to runTestIdsPort: [WinError 10049] The requested address is not valid in its context
Error: Could not connect to runTestIdsPort
Error[vscode-unittest]: TEST_PORT is not set.  TEST_UUID =  None
Error[vscode-unittest]: TEST_UUID is not set.  TEST_PORT =  45454
Plugin error connection error[vscode-pytest]: [WinError 10061] No connection could be made because the target machine actively refused it

Diagnostic data

• Python version (& distribution if applicable, e.g. Anaconda): 3.11.4
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
• Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

languageServer: "Pylance"

testing
• pytestPath: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: true

Extension version: 2023.20.0
VS Code version: Code 1.85.2 (8b3775030ed1a69b13e4f4c628c612102e30a681, 2024-01-18T06:40:10.514Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i7-1255U (12 x 2611)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	15.70GB (6.38GB free)
Process Argv	--crash-reporter-id 2780f478-1a55-4f3c-a0c3-cf90bbd5aa10
Screen Reader	no
VM	0%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
vscaat:30438848
vsclangdf:30486550
c4g48928:30535728
azure-dev_surveyone:30548225
0bi6i642:30933247
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019a:30933241

[eleanorjboyd]

Hi! Seeing Error: Could not connect to runTestIdsPort: [WinError 10049] The requested address is not valid in its context in your logs which means we are having trouble connecting between sockets we create for test run. Did you override localhost? You can check by calling ping localhost on your machine and see if the default has changed. If so you should be able to fix it if you remove that override.

[FrancaBa]

Hi Eleanor,
I don't think that I overwrote localhost. When running ping localhost, I get the following output:

[eleanorjboyd]

@karthiknadig, do you have another suggestion here on how to test for this?

[karthiknadig]

@eleanorjboyd When connecting from python we are using IPv4, the user has IPv6. We need to see how to support both scenarios.

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!

[eleanorjboyd]

This should be resolved as we have switched to using named pipes, thanks!