Run pytest in debug mode 'Debug Stopped' error message, check launch.json

[bverhoeve]

Type: Bug

Behaviour

When I run a test via pytest at the cursor in debug mode, the test run starts, and VSCode gives a popup with the title 'Debug Stopped' and opens the launch.json file. The test continues running according to VSCode but never terminates.

Expected vs. Actual

I expect the test to run and attach a debugger.
Actual behaviour, the window is opened, no debugger is attached and the test runs forever.

Steps to reproduce:

1. Write a test in pytest
2. Run test in debug mode
3. Crash

Diagnostic data

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

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

Multiroot scenario, following user settings may not apply:

envFile: "<placeholder>"

languageServer: "Pylance"

testing
• cwd: "<placeholder>"
• pytestEnabled: true

Extension version: 2024.2.0
VS Code version: Code 1.87.1 (1e790d77f81672c49be070e04474901747115651, 2024-03-06T00:22:39.156Z)
OS version: Darwin arm64 23.2.0
Modes:

System Info

Item	Value
CPUs	Apple M1 Pro (10 x 24)
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
Load (avg)	3, 4, 5
Memory (System)	16.00GB (0.10GB free)
Process Argv	--crash-reporter-id 70ecb779-06ee-4bba-8c0b-da256ce4378f
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30986171
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
pydisww1:30981707
cppperfnew:30979542
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
dsvsc020:30976470

[bverhoeve]

Screenshots to reproduce (I can't include the code as this is a private repository)

[bverhoeve]

The problem occurs as of version 2024.2.0 of this extension, 2024.0 still works.

[bverhoeve]

Hi this is currently blocking upgrades of the extension. Are there any workarounds for this problem?

[eleanorjboyd]

We have made substantial improvements to test debugging- are you still facing this issue?

[bverhoeve]

Hi @eleanorjboyd this has been resolved indeed.