Python tests stop button doesn't work

[willmckeandeb]

Type: Bug

I have Python tests configured with unittest. Once a test is in progress, there is a stop button on the testing tab that used to halt the currently running test. As of approx the last 3 weeks the stop button no longer works. Same applies to the stop button in the test results console tab.

VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:40:25.698Z)
OS version: Darwin arm64 22.1.0
Modes:

System Info

Item	Value
CPUs	Apple M1 Pro (10 x 24)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off 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)	27, 12, 10
Memory (System)	16.00GB (0.12GB free)
Process Argv	--crash-reporter-id b44b34bd-4b41-4224-b182-4a064da321c9
Screen Reader	no
VM	0%

Extensions (17)

Extension	Author (truncated)	Version
multi-cursor-case-preserve	Car	1.0.5
codealignment-vscode	cpm	2.0.19
vscode-eslint	dba	2.4.2
gitlens	eam	14.2.1
shell-format	fox	7.2.5
vscode-github-actions	git	0.26.1
code-groovy	mar	0.1.2
black-formatter	ms-	2023.4.1
python	ms-	2023.14.0
autodocstring	njp	0.6.1
vscode-xml	red	0.26.1
vscode-yaml	red	1.14.0
markdown-preview-enhanced	shd	0.6.8
swift-lang	ssw	1.4.0
shellcheck	tim	0.33.1
search	use	0.0.1
vscode-lldb	vad	1.9.2

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30792226
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
2e4cg342:30602488
f6dab269:30613381
showlangstatbar:30737416
03d35959:30757346
ecj1e332:30736112
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
diffeditorv1:30812748

[eleanorjboyd]

Hello! Is it possible for you to try this on vscode insiders with the newest version of the python extension? I think a recent fix I just put out two days ago might be the fix. If you can't try it you could also send over a minimal repro and I could try. Otherwise, I can keep this open till stable comes out. Thanks

[eleanorjboyd]

Following up I think this new PR is the fix #21876. I am assuming you are on the new testing rewrite since that has had reported problems similar to this but if you are not please let me know.

To see if you are on the rewrite, look to see if Experiment 'pythonTestAdapter' is active in your python logs. If you are unable to see the log for the experiment change your log level to info or trace and it should show up. Thanks!