python extension in remote connection is not setting TEST_RUN_PIPE

[msmitherdc]

Type: Bug

Behaviour

Traceback (most recent call last):
  File "/home/gridusr/.vscode-server-insiders/extensions/ms-python.python-2024.15.2024092502-linux-x64/python_files/unittestadapter/execution.py", line 274, in execute_eot_and_cleanup
    send_post_request(eot_payload, test_run_pipe)
  File "/home/gridusr/.vscode-server-insiders/extensions/ms-python.python-2024.15.2024092502-linux-x64/python_files/unittestadapter/pvsc_utils.py", line 335, in send_post_request
    raise VSCodeUnittestError(error_msg)
unittestadapter.pvsc_utils.VSCodeUnittestError: UNITTEST ERROR: TEST_RUN_PIPE is not set at the time of unittest trying to send data. Please confirm this environment variable is not being changed or removed as it is required for successful test discovery and execution.TEST_RUN_PIPE = 

Steps to reproduce:

1. Connect to remote docker container over ssh / tunnel
2. Configure test settings, in this case unittest
3. Test Discovery reports error. But tests discover, using django and unittest
4. Run tests with converage. Tests succeed but then trigger failure as coverage can't be evaluated due to connection failure for TEST_RUN_PIPE =(or so it appears)

Extension version: 2024.15.2024092502
VS Code version: Code - Insiders 1.94.0-insider (Universal) (c43f508b732d24b0c4732de9db2b38b4c5b88b8a, 2024-09-26T05:04:07.935Z)
OS version: Darwin arm64 23.6.0
Modes:
Remote OS version: Linux x64 5.14.0-427.33.1.el9_4.x86_64

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

User Settings

languageServer: "Pylance"

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

Installed Extensions

Extension Name	Extension Id	Version
GitHub Pull Requests	GitHub.vscode-pull-request-github	0.97.2024092604
JavaScript Debugger	ms-vscode.js-debug	1.94.0
Pylance	ms-python.vscode-pylance	2024.9.101
Python	ms-python.python	2024.15.2024092502
Python Debugger	ms-python.debugpy	2024.11.2024092501
Table Visualizer for JavaScript Profiles	ms-vscode.vscode-js-profile-table	1.0.10

System Info

Item	Value
CPUs	Apple M1 Max (10 x 2400)
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 skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	2, 2, 2
Memory (System)	64.00GB (3.09GB free)
Process Argv	--crash-reporter-id 35c15069-8b6b-40a5-be18-215ceeb83124
Screen Reader	no
VM	0%

Item	Value
Remote	Container docker-registry.rsgiscx.net:443/rsgis/grid:v2.0.0 (griddock) @ mds-devbox
OS	Linux x64 5.14.0-427.33.1.el9_4.x86_64
CPUs	AMD EPYC 7R13 Processor (4 x 0)
Memory (System)	30.65GB (6.87GB free)
VM	0%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256197
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
2i9eh265:30646982
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
9c06g630:31013171
a69g1124:31018687
dvdeprecation:31040973
dwnewjupyter:31046869
legacy_priority:31057981
nativerepl1:31134653
refactort:31084545
pythonrstrctxt:31093868
flighttreat:31119334
wkspc-onlycs-t:31132770
nativeloc1:31118317
wkspc-ranged-c:31125598
cf971741:31144450
e80f6927:31120813
pme_test_t:31118333
defaultse:31146405
ei213698:31121563
12bdf347:31141542
iacca1:31144502
notype1:31143044
b50ed353:31138333
showchatpanel:31139797
f8igb616:31140137

[eleanorjboyd]

Hi! This is a known error we are having where there is an issue sending a message even when everything else works right. We are fixing this as part of #23279. If the error is all you are seeing (and not any behavior issue with the extension) then I can follow back up when make the change- thanks!!

[msmitherdc]

Well I was trying the test the new coverage output from tests and as far as I can tell this was the reason that coverage could not be communicated. If this is not a real error, I will have to look more.

[eleanorjboyd]

Are you on the most recent version of the python pre-release? Could you check to see if you get Coverage data received. in your python output logs? You will need to set your log level to verbose which you can do by calling the command from the command palette "developer set log level" and rerunning the coverage request. Thanks

[msmitherdc]

Looks like this is being tracked here #24199

I am on the latest python prerelease and insiders. But I do not get the coverage data received. But seems like this is more an issue with the Django testing so I can close this here