python tests hang, won't restart, can't be stopped

[mgdelmonte]

Type: Bug

Starting happening just after last update. Python tests arbitrarily refuse to start, often after an existing test run is stopped prematurely with the "stop" button or with shift-F5.

VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Darwin arm64 24.2.0
Modes:

System Info

Item	Value
CPUs	Apple M1 Pro (8 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)	16.00GB (0.07GB free)
Process Argv	--crash-reporter-id a6c70ccc-c3da-4e63-bb46-cd57d3977060
Screen Reader	no
VM	0%

Extensions (37)

Extension	Author (truncated)	Version
ruff	cha	2024.56.0
doxdocgen	csc	1.4.0
mustache	daw	1.1.1
vscode-eslint	dba	3.0.10
gitlens	eam	16.0.5
prettier-vscode	esb	11.0.0
vscode-github-actions	git	0.27.0
terraform	has	2.34.1
better-cpp-syntax	jef	1.27.1
rainbow-csv	mec	3.13.0
vscode-azureresourcegroups	ms-	0.9.9
vscode-docker	ms-	1.29.3
debugpy	ms-	2024.14.0
mypy-type-checker	ms-	2024.0.0
python	ms-	2024.22.0
vscode-pylance	ms-	2024.12.1
jupyter	ms-	2024.11.0
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.0.21
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
remote-containers	ms-	0.394.0
azure-account	ms-	0.12.0
cmake-tools	ms-	1.19.52
cpptools	ms-	1.22.11
cpptools-extension-pack	ms-	1.3.0
makefile-tools	ms-	0.11.13
hide-gitignored	npx	1.1.0
vscode-print	pdc	0.13.2
vscode-yaml	red	1.15.0
openapi-vs-code	Red	0.5.10
lua	sum	3.13.4
even-better-toml	tam	0.19.2
ms-teams-vscode-extension	Tea	5.10.1
cmake	twx	0.0.17
vscode-mdx	uni	1.8.11
vscode-mdx-preview	xyc	0.3.3

(1 theme extensions excluded)

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31179979
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

[eleanorjboyd]

Hi! I think this might be related to a fix I just put in here: #24611. Are you on the pre-release version of the vscode-python extension? Tomorrow the fix will be out so if you could try it then and see if the bug persists that would be great! Thanks

[eleanorjboyd]

This should now be fixed on pre-release. Let me know if you are still seeing this issue and I will re-open, thanks

[sharmuz]

@eleanorjboyd Unfortunately I'm still experiencing the issue - testing remains perpetually stuck in discovery mode.

Python extension version: 2024.23.2024121801 (pre-release)
VS Code version: 1.96.1
OS version: macOS Sequoia 15.1.1

[mgdelmonte]

I'm seeing the same behavior -- happening less often, but still happening.

[dennymarcels]

Same here.

[Imanuel-Miz]

Same here, my original ticket is:
#24632

[Imanuel-Miz]

Hi @eleanorjboyd ,
Would appreciate any comment about this issue.
Thx

[omriperl]

Same for me... version 1.96.2

[Imanuel-Miz]

perhaps working on this one as part of: #24656
?

[omriperl]

@Imanuel-Miz the downgrade that was suggested in the link solved it! Thanks :)

[jpetot]

Same for me and it doesn't seem to work with Visual Studio Code - Insiders Version: 1.97.0-insider (Universal)

Could you reopen the issue?

[Imanuel-Miz]

@jpetot , I think we should all track #24656
My guess is there is some delay solving it due to the holidays (#24656 (comment))